>>from around the globe. It's the queue with digital coverage of Docker Con Live 2020 brought to you by Docker and its ecosystem partners. Welcome to the Special Cube coverage of Docker Con 2020. It's a virtual digital event co produced by Docker and the Cube. Thanks for joining us. We have great segment here. Precision cancer medicine really is evolving where the personalization of the data are really going to be important to personalize those treatments based upon unique characteristics of the tumors. This is something that's been a really hot topic, talking point and focus area in the industry. And technology is here to help with two great guests who are using technology. Docker Docker containers a variety of other things to help the process go further along. And we got here spring and who's the bioinformatics research assistant and Camille took Who's a student and in turn, you guys done some compelling work. Thanks for joining this docker con virtualized. Thanks for coming on. >>Thanks for having me. >>So first tell us about yourself and what you guys doing at the Children's Cancer Institute? That's where you're located. What's going on there? Tell us what you guys are doing there? >>Sure, So I built into Cancer Institute. As it sounds, we do a lot of research when it comes to specifically the Children's cancer, though Children a unique in the sense that a lot of the typical treatment we use for adult may or may not work or will have adverse side effects. So what we do is we do all kinds of research. But what lab and I love, which we call a dry love What we do research in silica, using computers at the develop pipelines in order to improve outcomes for Children. >>And what are some of the things you get some to deal with us on the tech side, but also there's the workflow of the patients survival rates, capacity, those constraints that you guys are dealing with. And what are some of the some of the things going on there that you have to deal with and you're trying to improve the outcomes? What specific outcomes were you trying to work through? >>Well, at the moment off of the past decade and all the work you've done in the past decade, we've made a substantial impact on the supply of ability off several high risk cancers in Pediatrics on and we've Got a certain Program, which spent I'll talk about in more depth called the Zero Childhood Cancer Program and essentially that aims to reduce childhood cancer in Children uh, zero. So that, in other words, with the previous five ability 100% on hopefully, no lives will be lost. But that's >>and what do you guys doing specifically? What's your your job? What's your focus? >>Yes, so part of our lab Old computational biology. Uh, we run a processing pipeline, the whole genome and our next guest that, given the sequencing information for the kids, though, we sequence the healthy cells and we sequence there. Two missiles. We analyze them together, and what we do is we find mutations that are causing the cancel that help us determine what treatment. So what? Clinical trials might be most effective for the kids and so specifically Allah books on that pipeline where we run a whole bunch of bioinformatics tools, that area buying thematic basically biology, informatics, and we use the data generated sequel thing in order to extract those mutations that will be the cancer driving mutations that hopefully we can target in order to treat the kids. >>You know, you hear about an attack and you hear Facebook personalization recommendation engines. What the click on you guys are really doing Really? Mawr personalization around treatment recommendations. These kinds of things come into it. Can you share a little bit about what goes on there and and tell us what's happening? >>Well, as you mentioned when you first, some brought us into this, which we're looking at, the the profile of the team itself and that allows us to specialize the medication on the young treatment for that patient on. Essentially, that lets us improve the efficiency and the effectiveness off the treatment, which in turn has an impact on this probability off. >>What are some of the technical things? How did you guys get involved with Docker with Docker fit into all this? >>Yeah, I'm sure Camille will have plenty to bring up on this as well. But, um, yes, it's been quite a project to the the pipeline that we have. Um, we have built on a specific platforms and is looking great. But as with most tools in a lot of things that you develop when your engineers eyes pretty easy for them to become platform specific. And then that kind of stuck there. And you have to re engineer the whole thing kind of of a black hole. That's such a pain to there. So, um, the project that Mikhail in my field working on was actually taking it to the individual's pools we used in the pipeline and Docker rising them individually containing them with the dependencies they need so that we could hook them up anyway. We want So we can configure the pipeline, not just customized based off of the data like we're on the same pipeline and every it even being able to change the pipeline of different things to different kids. Be able to do that easily, um, to be able to run it on different platforms. You know, the fact that we have the choice not only means that we could save money, but if there's a cloud instance that will run an app costal. If there's a platform that you know wanted to collaborate with us and they say, Oh, we have this wholesome data we'd love for you to analyze. It's over hell, like a lot of you know, >>use my tool. It's really great. >>Yeah. And so having portability is a big thing as well. And so I'm sure people can go on about, uh, some of the pain point you having to do authorize all of the different, But, you know, even though they Austin challenges associated with doing it, I think the payoff is massive. >>Dig into this because this is one of the things where you've got a problem statement. You got a real world example. Cancer patients, life or death gets a serious things going on here. You're a tech. You get in here. What's going on? You're like, Okay, this is going to be easy. Just wrangle the data. I throw some compute at it. It's over, right? You know what? How did you take us through the life? They're, you know, living >>right. So a supreme I mentioned before, first and foremost well, in the scale of several 100 terabytes worth of data for every single patient. So obviously we can start to understand just how beneficial it is to move the pipeline to the data, rather the other way around. Um, so much time would be saved. The money costs as well, in terms of actually Docker rising the but the programs that analyze the data, it was quite difficult. And I think Sabrina would agree mate would agree with me on this point. The primary issue was that almost all of the apps we encountered within the pipeline we're very, very heavily dependent on very specific versions off some dependencies, but that they were just build upon so many other different APS on and they were very heavily fined tuned. So docker rising. It was quite difficult because we have to preserve every single version of every single dependency in one instance just to ensure that that was working. And these apps get updated quite Simpson my regularly. So we have to ensure that our doctors would survive. >>So what does it really take? The doc arise your pipeline. >>I mean, it was a whole project. Well, um, myself, Camille, we had a whole bunch of, um, automatic guns doing us over the summer, which was fantastic as well. And we basically have a whole team of lost words like, Okay, here's another automatic pull in the pipeline. You get enterprise, you get to go for a special you get enterprise, they each who individually and then you've been days awake on it, depending on the app. Easier than others. Um, but particularly when it comes to things a lot by a dramatic pools, some of them are very memory hungry. Some of them are very finicky. Some of the, um ah, little stable than others. And so you could spend one day characterizing a tool. And it's done, you know, in a handful of Allah's old. Sometimes it could make a week, and he's just getting this one tool done. And the idea behind the whole team working on it was eventually use. Look through this process, and then you have, um, a docker file set up. Well, anyone to run it on any system. And we know we have an identical set up, which was not sure before, because I remember when I started and I was trying to get the pipeline running on my own machine. Ah, lot of things just didn't look like Oh, you don't have the very specific version of ah that this developer has. 00 that's not working because you don't have this specific girl file that actually has a bug fixes in it. Just for us like, Well, >>he had a lot of limitations before the doctor and doctor analyzing docker container izing it. It was tough. What was it like before and after? >>And we'll probably speak more people full. It was basically, uh, yeah, days or weeks trying to set up on in. Stole everything needed around the whole pipeline. Yeah, it took a long time. And even then, a lot of things, But how you got to set up this? You know, I think speculation of pipeline, all the units, these are the three of the different programs. Will you need this version of obligation? This new upgrade of the tools that work with that version of Oz The old, all kinds of issues that you run into when they schools depend on entirely different things and to install, like, four different versions of python. Three different versions of our or different versions of job on the one machine, you know, just to run it is a bit of >>what has. It's a hassle. Basically, it's a nightmare. And now, after you're >>probably familiar with that, >>Yeah. So what's it like after >>it's a zoo? It supports ridiculously efficient. Like it. It's It's incredible what Michael mentioned before, as soon as we did in stone. Those at the versions of the dependencies. Dhaka keeps them naturally, and we can specify the versions within a docker container. So we can. We can absolutely guarantee that that application will run successfully and effectively every single time. >>Share with me how complicated these pipelines are. Sounds like that's a key piece here for you guys. And you had all the hassles that you do. Your get Docker rised up and things work smoothly. Got that? But tell >>me about >>the pipelines. What's what's so complicated about them? >>Honestly, the biggest complication is all of the connection. It's not a simple as, um, run a from the sea, and then you don't That would be nice, but that know how these things work if you have a network of programs with the output of this, input for another, and you have to run this program before this little this one. But some of the output become input for multiple programs, and by the time you hook the whole thing up, it looks like a gigantic web of applications. The way all the connections, so it's a massive Well, it almost looks like a massive met when you look at it. But having each of the individual tools contained and working means that we can look them all up. And even though it looks complicated, it would be far more complicated if we had that entire pipeline. You know, in a single program like having to code, that whole thing in a single group would be an absolute nightmare. Where is being able to have each of the tools as individual doctors means we just have the link, the input on that book, which is the top. But once you've done that, it means that you know each of the individual pools will run. And if an individual fails, or whatever raised in memory or other issues run into, you can rerun that one individual school re hooks the output into whatever the next program is going without having one massive you know, program will file what it fails midway through, and there's nothing you can do. >>Yeah, you unpack. It really says, Basically, you get the goodness to the work up front, and a lot of goodness come out of it. So this lets comes to the future of health. What are the key takeaways that you guys have from this process? And how does it apply to things that might be helpful to you right around the corner? Or today, like deep learning as you get more tools out there with machine learning and deep learning? Um, we hope there's gonna be some cool things coming out. What do you guys see here? And the insights? >>Well, we have a section of how the computational biologist team that is looking into doing more predictive talks working out, um, basically the risk of people developing can't the risks of kids developing cancel. And that's something you can do when you have all of this data. But that requires a lot of analysis as well. And so one of the benefits of you know being able to have these very moveable pipelines and tools makes it easier to run them on. The cloud makes it easier to shale. You're processing with about researches to the hospitals, just making collaboration easier. Mainz that data sharing becomes a possibility or is before if you have three different organizations. But the daughter in three different places. Um, how do you share that with moving the daughter really feasible. Pascal, can you analyze it in a way that practical and so I don't want one of the benefits of Docker? Is all of these advanced tools coming out? You know, if there's some amazing predicted that comes out that uses some kind of regression little deep learning, whatever. If we wanted to add that being able to dock arise a complex school into a single docker ice makes it less complicated that highlighted the pipeline in the future, if that's something we'd like to do, >>Camille, any thoughts on your end on this? >>Actually, I was Sabrina in my mind for the last point. I was just thinking about scalability definitely is very. It's a huge point because the part about the girls as a technology does any kind of technology that we've got to inspect into the pipeline. As of now, it be significantly easier with the use of Docker. You could just docker rise that technology and then implant that straight into the pipeline. Minimal stress. >>So productivity agility doesn't come home for you guys. Is that resonate? >>Yeah, definitely. >>And you got the collaboration. So there's business benefits, the outcomes. Are there any proof points you could share on some results that you guys are seeing some fruit from the tree, if you will, from all this Goodness. >>Well, one of the things we've been working on is actually a collaboration with those Bio Commons and Katica. They built a platform, specifically the development pipelines. We wanted to go out, and they have support for Docker containers built into the platform, which makes it very easy to push a lot of containers of the platform, look them up and be able to collaborate with them not only to try a new platform without that, but also help them look like a platform to be able to shoot action access data that's been uploaded there as well. But a lot of people we wouldn't have been able to do that if we hadn't. Guys, they're up. It just wouldn't have. Actually, it wouldn't be possible. And now that we have, we've been able to collaborate with them in terms of improving the platform. But also to be able to share and run our pipelines on other data will just pretty good, >>awesome. Well, It's great to have you on the Cube here on Docker Con 2020 from down under. Great Internet connections get great Internet down. They're keeping us remote were sheltering in place here. Stay safe and you guys final question. Could you eat? Share in your own words from a developer? From a tech standpoint, as you're in this core role, super important role, the outcomes are significant and have real impact. What has the technology? What is docker ization done for you guys and for your work environment and for the business share in your own words what it means. A lot of other developers are watching What's your opinion? >>But yeah, I mean, the really practical point is we've massively increased capacity of the pipeline. One thing that been quite fantastic years. We've got a lot of increased. The Port zero child who can program, which means going into the schedule will actually be able to open a program. Every child in Australia that, uh, has cancel will be ableto add them to the program. Where is currently we're only able to enroll kids who are low survivability, right? So about 30% the lowest 30% of the viability we're able to roll over program currently, but having a pipeline where we can just double the memory like that double the amount of battle. Uh, and the fact that we can change the instance is really to just double the capacity trip. The capacity means that now that we have the support to be able to enroll potentially every kid, Mr Leo, um, once we've upgraded the whole pipeline, it means will actually be a code with the amount of Children being enrolled, whereas on the existing pipeline, we're currently that capacity. So doing the upgrade in a really practical way means that we're actually going to be a triple the number of kids in Australia. We can add onto the program which wouldn't have been possible otherwise >>unleashing the limitations and making it totally scalable. Your thoughts as developers watching you're in there, Your hand in your hands, dirty. You built it. It's showing some traction. What's what's your what's your take? What's your view? >>Well, I mean first and foremost locks events. It just feels fantastic knowing that what we're doing is as a substantial and quantify who impact on the on a subset of the population and we're literally saving lives. Analyze with the work that we're doing in terms off developing with With that technology, such a breeze especially compared Teoh I've had minimal contact with what it was like without docker and from the horror stories I've heard, it's It's It's a godsend. It's It's it's really improved The quality of developing. >>Well, you guys have a great mission. And congratulations on the success. Really impact right there. You guys are doing great work and it must feel great. I'm happy for you and great to connect with you guys and continue, you know, using technology to get the outcomes, not just using technology. So Fantastic story. Thank you for sharing. Appreciate >>you having me. >>Thank you. >>Okay, I'm John for we here for Docker Con 2020 Docker con virtual docker con digital. It's a digital event This year we were all shale three in place that we're in the Palo Alto studios for Docker con 2020. I'm John furrier. Stay with us for more coverage digitally go to docker con dot com from or check out all these different sessions And of course, stay with us for this feat. Thank you very much. Yeah, yeah, yeah, yeah, yeah, yeah

>>from around the globe. It's the queue with digital coverage of Docker Con Live 2020 brought to you by Docker and its ecosystem partners. Everyone welcome back to Docker Con 2020 Docker Con 20. I'm John Furrier, host of the Cube. We're here for virtual event docker con docker, con dot com, and check out all the great footage. And also great guests were talking to all the major thought leaders and people in the industry making it happen as we have this new reality, a great guest and a great segment here from Engine. It's now part of F five, Robb said. Who's the vice president? Product management Sydney, thanks for coming on this segment. Appreciate you taking the time to chat with us. >>No problem. Happy to be here >>so and UNIX Everyone that does development knows about you. Guys have been very popular product with developers. Number one in the Docker hub will get to that later on this segment. So it's known really in the industry is really easy, easy to use and very reliable component of cloud native and cloud, if you will Anything that working So So I got I got to ask you with the new reality we're living with Covert 19 we now see the new reality that's now apparent to everyone in the world that with new work style, working at home VPNs are under provision now. People working from home, more service area with security. The at scale problems are surface for the executives and business, saying, We need to figure this new reality out because this is not going to change. It's going to move to hybrid when it comes back. But ultimately it exposes and highlights the opportunities around cloud native and kind of shows the operating model of how applications are going to be using. So I think this is going to be mainstream trend for what used to be an inside baseball kind of industry. Conversation around micro services, containers, docker containers, kubernetes. This is all now a tailwind for what will be a massive surge in new APS. I want to get your thoughts and reaction to that as you guys are in the middle of it with your product and the developers would have to build new value on top of it. What's your reaction? >>Yeah, I think you're absolutely right. We're also dealing with our own version of this new way of working right. We're also working from home and working remotely and seeing how that impacts us. But as we think about our customers and the folks that leverage in genetics, we started with scaling applications. We have 10 X solution that made it easier to deploy an application, have it scale in a very efficient way. And so it's folks are moving online more and more, relying more on staying connected, no matter where they're working from. Providing that capability is something that's going to continue to be core and will increase in importance. And these folks are looking to build more modern applications or modernize what they already have. Leveraging our technologies is just a natural extension. It's the technology they're already familiar with. They've been relying on it for many years and, you know, as they look to the future, has the capabilities they need to continue to rely on it going forward. >>What are some of the new things that you're working on? You can share with the audience because you're known for tried and true, very reliable. Okay, now you got micro services, which is emerging and very dynamic, literally, figuratively. So what's the new stuff? What do you guys focused on? Can you share some insights into how you're thinking about it and some things that you're doing? >>Yeah, a big part of what we're focusing on is really taking with headaches that come with scaling up applications, especially in the modern world. Now, those headaches are all about understanding the complexity of these new applications, being in the confidence needed to be able to deploy them at scale and understand not only what they're doing, but make sure that if something were to go wrong, they could figure out what was happening. And so, as we think about the investments we're making at the help folks modernize versus just making it easier to employ at modern applications of scale, which is one category of things, second is making sure that you have a really strong understanding of how the application is really working, so that, you know, with if it breaks, it could be fixed quickly. But there opportunities to improve it. We can quickly see the impact of it, and, you know, there's a lot of capabilities we're building in on those two dimensions. And in the third dimension, I would say is around security. I think there's a lot of new surface area. It's being exposed as folks start to build more micro services based applications. And you know, with the technology we have way allow people to buy both rich security capabilities as well as very surgical capabilities, depending on where they need the right functionality. >>And the container business has been really great ride to watch the rise of containers that really someone who has been in software engineering since I was 17. You know, the old way of systems thinking is modernized with containers, and you saw that the beginning of a surge of a sea change Now, actually, with micro services, you just pointed out it's gonna create a whole nother level level of head room. But containers really brought in this notion of making systems work better together, and I think that's really been a great boon for developers. So I got to ask you, you know, Docker containers and now kubernetes on this trend, you guys have been very popular, if not the most popular downloaded container in the hub, and so you've been super popular developers. So what happens next? First? Well, why is that the case and talk to the developers? Why will you continue to be popular? What do you guys have got to keep that that satisfaction going. Why so popular? And how are you going to keep that rolling? >>Yeah, I think. Why so popular? I think we've been fortunate to ride the wave of trusted solutions, right? So folks were already leveraging us for their critical applications. I've been very critical location. It's natural to look to that same text technology as you move to new environments. And, yeah, we've been very fortunate. Teoh have folks continue to trust us with their applications as they move to new environments as a containerized things. And we appreciate that. And we continue to invest in making sure that our feature set is just as capable in those environments as it is anywhere else. And in addition to that, we do invest heavily in making sure that our capabilities and those in the container, space and micro services space specifically, are you staying ahead of where there's a lot of work we're doing to support the next generation capabilities that folks want to be able to leverage but aren't necessarily yet. And that scales from kind of near term things like like G rpc all the way out to HDP three. That's on the horizon. So as we look at the space, we're privileged to have the footprint already. But at the same time, we're not resting on our laurels. We're absolutely investing and making sure that we allow folks to continue to deliver that high quality, high performance application experience no matter what environment they choose to use. >>You know, you know, this whole covert crisis brings up the glass is half full or half empty, depending on your view is you know that due to the two worlds are certainly getting more collision oriented when it come together. The CSO level size of sides of the business and the developer side. We've always said for years other developers on the front lines and it's true, have been cloud native and cloud has been great for developers, but now more than ever, the conversation having on the business side would CSO CIO, CIO, CSO, or whatever have been Hey, my house is on fire after I don't have worry about I don't need to worry about the appliances and what's going on in my kitchen. I need to save my business. And so they're then gonna call the developers to the table. And you're seeing this this kind of formation of critical path thinking around OK, we need to come out of this crisis on a reinvention growth trajectory, which brings the developers into the mix even faster. So I want to get your thoughts on that because, you know, what does that actually mean? Are they gonna be called in for projects? I mean, what's the media's look like? Because you have a zoom meeting or whatever this is going to be now a new dynamic, A new psychology of the business models of these companies with developers are going to be very active leaders in that new role. Because the virtualized world, now that we live in, is going to be different. The applications have more demands and more more needs more capabilities. So take us through your thinking on this and what what should developers expect when they get called to those meetings? >>Yeah, I think you know the trend that we're seeing that's going to accelerate. I believe as a result of this is the internal transformation. So there's a lot of technologies that developers already leverage be able to deliver that absent. There's technologies that they'd like to be able to leverage more and more, especially if they're using more modern environments. And that tends to come into sharp relief against the legacy infrastructure that exists in the legend legacy tooling that oftentimes exists in large organizations. And so, as organizations start to see, not only about the in the world has changed prior to code, and they need to modernize and transform. I think you know this. This crisis will also spur folks toe really put more thought into how they operate. We're already looking at from the remote work perspective, but also the agility that businesses really want to be able to have but traditionally have been prevented from having. And so I think that the developers are really gonna have an opportunity here to really drive that agile change they want to see in an organization so they can get the capabilities they want help to market quickly. That's going to require new tools, new processes within the organization and those types of things that we're fully supported about. We work in legacy environments, work in modern environments. We allow companies to be as agile as they like to be. I think developers have a really good opportunity here to really be leaders of that change. >>That's awesome. Great insight. So let's talk about the developer side. I'll put my developer hat on for a second here. Sydney. OK, The business guys came to me. We're gonna We're gonna do more cool stuff. I get that. That's totally relevant. Very good insight there. But now in the developer and I have been working with engineers, and I know of Engine X. What's in it for me? What's in it for me? The developer? What do I need to know about Engine X now for me, as a developer, going forward? >>Look, I mean, way come from a really strong, open source tradition. And you know the main reason folks use our solutions. Because if we take headaches away right, I mean, we're a tool that allows folks to deliver their applications, deploy their applications without having to worry about the mechanics. And so for the developers, you know what's in it for you is you build, the application will take care of. The rest will make sure it gets delivered with the controls that are required with security and authentication is required. We operate as an extension of your application. We provide a lot of nice things in the front door. All the way back to you know, into the bedroom is technically a spark, as the application infrastructure is concerned. But, you know, we take care of that common infrastructure. They keep infrastructure set of capabilities needed. That application. Developers can simply focus on building the best applications they can, and we'll make sure that they were >>awesome. Now let's get into the F five acquisition combination with Engine X. What does that do for you guys? As a change of capabilities as it increased more head room for solutions? Is there a new joint tech take us through some of the impacts of that combination? >>Yeah, so it's been a good right. It's been just over a year since the deal closed, and we've been aggressively investing in scaling up the vision that we had previously have. We really want to bring applications to life. You make it so that your application not only scalable and highly available, but it's able to adapt over time. And that, of course, would require input from operations teams, of course, but you know, we're trying to make sure that folks have the ability to operate their applications under any circumstances, whether they're being attacked, whether they're under high demand, whether people are moving all over the place, and we're really trying to make it so that the application is essentially bullet proof. So with that five, we have the ability to invest more in that road map in that vision, in addition to bringing on some pretty cool, complimentary capabilities. One of the things that we're really happy to see is the rich security capabilities that five have has that we're now able todo leverage with the Internet solutions side by side, providing no again new ways to get really advanced security capabilities into the right places in your application greeting. Yeah, >>great insights. I really appreciate that That commentary love to get your thoughts on just something that's always been near and dear to my heart, being cloud world since the early days and trying stuff. Now it's fully enterprise ready and doing all sorts of new things that multi cloud hybrid. But remember the days back when Dev Ops was kind of debated? All that is the day of is it ops? And it always had that Dev ops kind of. I'm an operations person or a devil developer. That's kind of generally been resolved in the sense that infrastructure is code is kind of resolve that. But now, with the Covad crisis, you're seeing operations clearly front and center again, right? So you got security ops now coming online, networking up. So I think the new reality and the edge exploding people are home. That's technically an edge. Perimeter security is now the edge point. More and more edge is more and more network traffic is getting more and more complicated. This >>is >>put bring up a lot of conversation around. What is the new formula As you navigate this, how do you attack the problem? Space is how do you create solutions? Is there a playbook? Is there anything that you could share in terms of this new thinking? Because it's gonna be a new trajectory. I think this is an inflection point came from explosions coming of APS. I believe we've been reporting on that. But the thinking has to change. It's going to be pretty crazy. What's your what's your thoughts on this? >>Yeah, I think folks are getting more and more experience with this new way of working on infrastructure of code is absolutely here. Um, automation is absolutely your orchestrations. Absolutely here. And so I see no more and more of these capabilities will get stitched together. And as I said earlier, you know this this organizational transformation It's all about taking the human more and more out of the loop for certain things to be ableto benefit or to the benefit of being able to move more quickly, but in a predictable way. So you're living failures that come with moving quickly. But you're getting that elasticity that you really want. And so, yeah, I think there's more, more adoption of practices. It's not gonna be overnight for folks. But I do think again, this this crisis is gonna give folks an opportunity to really take a deeper look at how they've been operating and where they want to get to, and it's gonna provide an opportunity to accelerate that move, >>you know, from a developer's perspective. The tried and true form of making something complex, easy with us through abstractions making highly performing and highly available. Always a good formula, right? I mean, as the world gets more complex, you still got to move packets around. You still got to run applications. It's just gonna be that tried and true formula of reduce the complexity, make things easier but makes things run faster, make things runs higher scale. This seems to be the play book. What's your thoughts? >>Yeah, absolutely. You know, things that once were hard to becoming easy. And I think we look back three years. Five years from now, we'll see a world that's that's even more automated, moving much more quickly. And some of the things that look difficult now are gonna become commoditized, right? So, you know, as I talked about bringing applications of life and making applications more resilience, more able to protect themselves more ableto, he'll defend all that kind of stuff. The things that the advanced things that we're doing now that folks are playing with will become the easy things, and we'll have new challenges to focus on, especially as we look at things like Ai. We're really starting to get a sense for some of the capabilities we can apply Teoh impact application behaviors and performance. But once you get to the point where you build up a good library of capabilities now, you really have a nice playbook that can become a foundation for even more advanced things. >>Yeah, build that foundation. Scale it up. It's beautiful scales and new competitive Advantage. Lovett Final question. Just take a minute to give the plug for Engine X. Really appreciate your insights here in this segment on this new reality, this new new developer environments going to be huge. Give the plug for engines. What are you guys working on? What should people know about share? What's happened? >>Yeah, so Internet spent, you know, the last decade plus making applications work at scale. I'm really focused now on making applications easy and bringing them to life. And so, you know, the laser focus we have is on taking away the headaches that folks might have, you know, as they try to scale up on their applications. So we're focused on that space we're focused on taking with headaches that folks have is they're trying to make sure that the applications more secure we're taking away the headaches of folks have is they're dealing with complexity of applications. Um, and 80 eyes. You know, that's that's the hottest thing. Right now, people are talking about applications, but they're actually talking about AP eyes that needs to be leveraged, to be able to make their applications really saying so, you know, in all of those spaces, our focus is on making modernization much easier And taking where the headaches associated with doing so. >>Sidney, wrap side with VP of product management at engine X now part of F five. Great conversation. Um, him up on Twitter. He's out there. Great conversation with the community. Really appreciate you taking the time. Thank you. >>Thank you. >>Okay. Him up on Twitter? If any questions jump into the event, this is Docker con 2020. I'm John Furrier here in the Palo Alto studios. Getting all the moat interviews as fast as we can get them to you. Here is Docker con segment. Thanks for watching. Yeah, yeah, yeah, yeah, yeah

>> Announcer: From around the globe, it's theCUBE. With digital coverage of Dockercon live 2020. Brought to you by, Docker, and its ecosystem partners. >> Hey, welcome back everyone to the DockerCon 2020, #DockerCon20. This is The Cube virtual coverage with Docker on their event here. And we're in the studio in Palo Alto, I'm John Furrier your host of theCUBE, we're here with a great guest to talk about Docker Desktop, the Microsoft relationship, and the key news that's coming out. Ben De St Paer-Gotch is the product manager for Docker Desktop. Ben, great for coming on, thanks for spending the time with me. >> Thanks for having me, I really appreciate it. >> So obviously, this is a virtual conference, we wish we could be in person, but given the state of affairs we're going to do remotely, but the momentum Docker has is phenomenal, it's always been great with containers. It's the number one downloaded app around for developers. Microsoft just had their Build conference, which was again virtual as well, or digital, as they say, it's interchangeable. But clear momentum now with Docker as containers actually is the standard, you guys are doing great. What's the key news out of the Microsoft world for people who missed it last week with MS Build? >> Yeah, so last year at Build, Microsoft announced WSO2 to the Windows subsystem with Linux two. (mumbles) The mapping between the windows (mumbles) Which, went really well but it just didn't provide the same centered needed Linux experience. Last year, they announced Windows subsystem Linux two, (Provides an actual Linux one on windows machine, and we've been working hard with Microsoft over the last year to integrate proper desktop as a main desktop application for working with containers with WSO2. A build this year, Microsoft has gone on and announced that WSO2 is going to have a few new features, and it's going to have new features. (mumbles) Mention Linux graphical, Linux applications, you can access the file system, the installation is going to become a slicker which I guess I'm the most excited about that pitch. But the most exciting announcement is, they will be bringing GPU support to WSO2 which means that we will be able to provide and give you support through Docker desktop or container workloads that peoples are working on. And now we're launching Gray and Agua through containers and docks and desktops and Windows which is really cool because we haven't been able to do that before. >> So is this the first GPU support on Microsoft Windows for Docker, with Docker? >> It's, yeah, it's the first GPU Support for Docker Desktop or Mac or Windows. So, previously the hypervisor hasn't passed through the GPU, pretty much, which meant that we couldn't access it from Docker desktop. So Docker desktop isn't about a lightweight VM we sorts of plumb all that in for you. But we're limited about what we could get access to from the hypervisor, Microsoft putting this through and giving us access for the first time, we can actually, we can go. >> Not to go on a side tangent here, but you know, all these virtual events, and I was watching some of the build stuff as well, as well as us immediate streamers and doing stuff, you can see people's home rigs. And you talk to any Developer, video streamer, or anyone who is working remotely, if you don't have the best GPU's in there, I mean, this has just become, I mean, quite frankly, you need the GPU's. So this is important, it's not only from a vanity standpoint performance. Having that support, I'm going to want the best GPU's, I'm always going to be upgrading my machine for that extra power. What's the impact? What does it mean for me as a Developer? Does it increase stuff? What's the bottom line? >> As a Developer, it means you actually have access to it. So, especially when you're doing workloads on the CPU, you've got minimum amounts of power utilization you can do. When you're running workloads for an L Development, you have a lot of power up process you've got to log, to do your mobile training. So, in an element cycle, you're likely to have your application which you're going to use to produce a modeling, you're going to have training data. Taking that training data and producing a model requires lots of panel processing which is an enormous calculations in producing with finer waitings. Doing that on a CPU has to be done on a serial fashion rather than parallel, which is huge and intensive and takes a really long time. Whereas on a GPU, you can do all of that in parallel which massively reduces the amount of time it will take to run those training functions. Either just straight up in Linux or running them in a container, which as the more of people are looking at running container with workloads, it's how I first, the first team that I was on actually used Docker. I was working in Amazon Alexa, and my team picked up the opportunity to run our workload in container. And that was my first experience, so even though my team backed down, so I could see the system. >> Yeah, ML workloads automations could be critical of that performance. Okay, let's get into some of the momentum with Microsoft, you guys have obviously, builds over, we're here now at DockerCon, there's news. Could you share some of the tidbits for what's being talked about now with Docker and DockerCon. >> Yeah, absolutely, so, along with everything else we've been doing, we've been partnering with Microsoft trying to make the best experience generally with Docker desktop, and with WSO2 and with the VSCO. I've been working closely with Microsoft guys to actually try and improve our experience in Windows as it is today, and to improve some of those integrations with VSCO, and also working with the VSCO team on the Docker plugin for VSCO to give our feedback, and to hear feedback from those guys on the errors and issues they're seeing with Docker desktop and to really try to produce the best experience we can on Windows. End to end, from very front end running all the way through that first push, that first run on the cloud using Docker. >> So what is some of the new product management processes and customer support things that you guys are doing? This comes up a lot, obviously, we had a great conversation around shift left with security. That's great news there. You start to see a lot of this added value for Developers, wanted their support right? So how do I get things I need, and from a customer standpoint? It's kind of a moving train this world and it's only getting better and better from a Developer standpoint. But there's more complexity, it's got to be abstract the way you've got, you know, this new abstraction layers developing. You've got a lot of automation. How does the customer get the support they need in the same agile way that Developers are cranking out code? >> It's a really good question, it's something I think we're still working on as well. So, we're trying to working out and one of the big things I'm trying to work out is, how to make it easier for people to get started with Docker, and how do we also make sure with the things we build, we don't leave a cliff edge instead of a lining path. You don't get to a certain point in an easy process, and then the next step, takes you straight off a cliff, so that's not useful for anyone. So, producing those parts and those ways for people to learn and actually progress is something we're really trying to work out. How to make it natural from the first experience all the way through. From an actual support perspective, the other thing we're looking at, is we're trying to do more things in the open. We're really trying at Docker to bring as many of the new features and pieces we're developing which we have to do that in the open with community visibility, so that if people really want it fixed, they can open the PR and they can help us out. And then the last thing that my team really stood out was our Docker of having actions. As creators, someone already finished, could you do this? Someone else had a PR and emerged it. So, to a certain extent, you've got your one side which had you on board and this ever growth spiral and you keep learning. The other side is how'd you fix the board when you find an issue? In that one, we're really trying to work with the community, a lot more than we have in the last couple of years. >> Awesome, some folks watching, hit him up on Twitter, he's the Product Manager for Docker Desktop among other things. You guys are very transparent, you've got your Twitter handle on the lower third. People can chime in or just jump on the chat, we'll follow up and get you the info. Final question for you Ben, as you look at this reality we're in, there's kind of a holistic kind of moment now where people kind of realizing the new realities here. You're looking at the.. you get the keys to the kingdom with Docker Desktop, okay. You got some momentum with Microsoft, the developer role is moving fast and fast as the head room increases for capabilities with automation. And I know you mentioned a few of those things. GPU is now available. What's the future look like for these Developers? The next short, medium and long term? What's your view as you look out over the landscape because you've got to look at the product roadmap, your engagement with the community. Can you share some insight into how you're thinking about Docker Desktop going forward? >> Yeah, absolutely. So, I think what really interesting point as you say, which is that, if you look at sort of a lot of the Developer side of things that have sort of come out in the last like six months, six to eighteen months. The things I see, I see daily like you mention, things like orchestrating for containers gaining momentum. If you think about crossing the Kaizen model, we're just passed the early Dockers now. We're kind of into the early majority, but we're going to start to move over the next few years into the late majority. What that really means is that people here have been using one of two of these technologies. Maybe you've been using cloud, maybe you've been using Edge, maybe you've been using containers, maybe you've been using CICD, maybe you are using Expiration, maybe you're not. Maybe you've got a Microservice application, maybe it's a little bit of a mole rat. What we're really going to see is, you're going to start to see, all of these changes intersecting and overlapping. And people who have started to pick up model two of these will start to pick up all of them. And that's probably going to happen as we move into the majority of users. So from a what's coming instead of a lot of those thing that you see in best practice in the ideal Developer setup, so a beautiful CICD, a more of an orchestrated environment, Microservice architecture, we're going to see a lot more of that becoming the norm. But I think along with that, we'll also see a level of recognition coming along that a single Microservice alone doesn't provide value. And that's it's going to be some of those groups of services that will provide the user outcome. And that's where my focus is at the end which is you know, an authentication service is great but it doesn't provide value unless you give access to something as authentic. >> It's been issued that the new Docker is all about Developer experience. This is really the core mission. I mean, since the sale of the piece of morantis, Docker has retrenched and reinvented, but stayed core to its principles. Just share with the Developers who've been watching that are coming back into the ecosystem, what is this new Docker vibe? Share your thoughts. >> The new Docker vibe is about working in the open, and it's about solving problems for Developments. The original goal of Docker was to make it easy to pack and ship. It was to reduce Developer friction. As we move more into, sort of, the enterprise space, we worry more about Ops and DevOps. We're not trying to re-focus on Developer and if you sort of think there's two parts to the Developer life cycle, where you've got your work, where you're doing your creative work, where you're writing code. And then you've sort of got your part of the inner loop. And then you've got your part where you're trying to get that code out to production, you're trying to get your value to someone else. Instead of your outer loop, we're really trying to focus on the inner loop And sort of our mantra is that any bit for a Developer should spend as much as their time as possible creating new and exciting things and we're onto those holes that reduce those boring, Monday, repetitive tasks, that we're really trying to work out how we take those boring repetitive pieces and how do we make them just vanish like magic from new users or how do we reduce the friction for the experience from users? From both desktop and hub, we're really trying to bring those two together to achieve that. >> You know what's great about folks who have been in the class since day one. All of us have scar tissue experiences, you know the one thing that's constant is constant change. And one of the things that you guys have done at Docker, and hats off to the whole, you know, original team, is that brand of Docker has symbolized quality openness, and set the standard, I mean, if you look back and containers were really coming around, it's not a new concept. But Docker really set the industry on this path and it's been great to follow every DockerCon at TheCube coverage, but more importantly, as the demand for Developers to build these next wave of Cambrian explosion of applications. It's going to be more important than ever to have more of these abstractions, more of these tools in this real time, more Developers experience because there's more building going on. And it's not just one cloud, it's all clouds, it's all things. >> Yeah, I think it was like when IDC analyzed the future report a couple years ago, I think it was maybe the 2018 one. They said that maybe 2017. They said to date, we've built 500 millions applications worldwide and by 2023, we'll build another 500 million. The rate of creation is just insane, it's exponential growth of us producing more and more applications and connecting more and more devices to do them. The sheer volume of creation and the rate of new technology supporting, even with the rate of companies adopting, I guess more of a warm cloud. I think it's like 60 percent of companies are now more than one cloud provider. Maybe even more, maybe it's like 80 percent. It's ridiculous. >> I was just having this debate on Twitter about this multi-cloud. Someone tried to call us out saying, "Oh you guys were pooing on multi-cloud in 2016 and 18." I go "Look at, no one was Pooping on multi-cloud, it didn't exist." I had multiple clouds but there was no real use case. Now you're starting to see the use cases, where yeah, I had multiple clouds and I got Azure here, I got this over here. But no one wakes up and spreads their workloads wrong. This is going back a few years. Certainly the hybrid was developing, but I think now you're starting to see with networking and some of these inter-operable dynamics, you start to see innovation pockets in wide spaces in large market opportunities for start-ups and companies to thread the clouds together at the right place. So I think multi-cloud is becoming apparent from a use case stand point. Still a ton of work to do, I mean direct connects, got SLA's, I mean all kinds of stuff at the networking level but it is real. It's going to be one of those realities that everyone has, at least one or two, if not three. It could be optimization, this is what Developers do right? Solve problems. >> Yeah, absolutely, I mean if nothing else, I've encounter a couple of companies even just where redundancy is handled by multi-cloud strategy. If you want to achieve more nines and you're just balancing workloads between two clouds. >> I mean, the Zoom news was really a testament to that because everyone got into a twist over that. Oh Zoom moves off Amazon, no they didn't move off Amazon, they went to Oracle, they got Adge, they're everywhere. Why wouldn't they be? They need to pass it, they fail over, they need fall tolerance, I mean, these are basic distributing computing concepts that is one on one. You've got to have these co-locations. And optimization for those clouds and the apps on Microsoft as well, so why wouldn't you do it? >> Exactly. And that's that hybrid, that multi-cloud, compounding that some of which you said earlier, that over changes when you're looking at how you go to CICD, how you're bundling these applications, creating more applications than ever. Coming back, sort of, with more AI workloads, much like GPU and you combine that with, sort of, last in the growth of age devices as well. It sort of makes for a really interesting future. And Docker is sort of, that summation SOV, what we're using to frame how we're thinking about our product and what we should be building. >> Great, for the audience out there, hit him up on Twitter, Ben's available, they're out in the open, if you're interested in how Docker makes life easier on the Windows platform, with the GPU support, they've got security now built in, shifting left. Give these guys a call and of course, we love the mission, out in the open. It's theCUBE's mission as well and great to chat with you. Ben, thanks for spending the time with me today. >> Been an absolute pleasure, thank you for having me. >> Okay, just TheCube's coverage, the virtual Cube with DockerCon co-creating together out in the open. DockerCon20, #Docker20, I'm John Fer with TheCube, stay tuned for our next segment, and thanks for watching. (ambient 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)

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

>> Narrator: From around the globe it's theCUBE with digital coverage of DockerCon Live 2020. Brought to you by Docker and its ecosystem partners. >> Hi, I'm Stu Miniman and welcome to theCUBE's coverage of DockerCon Live 2020. Really excited to be part of this online event. We've been involved with DockerCon for a long time, of course one of my favorite things is always to be able to talk to the practitioners. Of course we remember for years, Docker exploded onto the marketplace, millions of people downloaded it, using it. So joining me is Hui Xue, who is a Principal Deputy Director of Medical Signal Processing at the National Heart, Lung, and Blood Institute, which is part of the National Institute of Health. Hui, thank you so much for joining us. >> Thank you for inviting me. >> So let's start. Of course, the name of your institute, very specific. I think anyone in the United States knows the NIH. Tell us a little bit about your role there and kind of the scope of what your team covers. >> So I'm basically a researcher and developer of the medical imaging technology. We are the heart, lung and the blood, so we work and focus on imaging the heart. So what we exactly do is to develop the new and novel imaging technology and deploy them to the front of our clinical library, which Docker played an essential role in the process. So, yeah, that's what we do at NHLBI. >> Okay, excellent. So research, you know, of course in the medical field with the global pandemic gets a lot of attention. So you keyed it up there. Let's understand, where does containerization and Docker specifically play into the work that your team is doing? >> So, maybe I'd like to give an example which will suffice. So for example, we're working on the magnetic resonance imaging, MRI. Many of us may may already have been scanned. So we're using MRI to image the heart. What Docker plays, is Docker allow us to deploy our imaging technology to the clinical hospital. So we have a global deployment around 40 hospitals, a bit more, around the world. If we are for example develop a new AI-based image analysis for the heart image, what we do with Docker is we can put our model and software into the Docker so that our collaboration sites, they will pull the software that contains the latest technology, then use them for the patients, of course under the research agreement at NIH. Because Docker is so efficient, available globally, we can actually implement a continuous integration and testing, update the framework based on Docker. Then our collaborators would have the latest technology instead of, you know, in the traditional medical imaging in general, the iteration of technology is pretty slow. But with all this latest technology, and such like container Docker come into the field. It's actually relatively new. In the past two to three years, all these paradigm is, it's changing, certainly very exciting to us. It give us the flexibility we never had before to reach our customers, to reach other people in the world to help them. They also help us so that's a very good experience to have. >> Yeah that's pretty powerful what you're talking about there rather than you know, we install some equipment, who knows how often things get updated, how do you make sure to synchronize between different locations. Obviously the medical field highly regulated and being a government agency, talk a little bit about how you make sure you have the right version control, security is in place, how do all of those things sort out? >> Yes, that's an essential question. So firstly I want to clarify one thing. So it's not NIH who endorse Docker, it's us as researchers. We practiced Docker too and we trust its performance. This container technology is efficient, it's globally available and it's very secure. So all the communication between the container and the imaging equipment is encrypted. We also have all the paperwork it saved to set up to allow us to provide technology to our clinician. When they post the latest software, every version they put up into the Docker went through an automated integration test system. So every time they make a change, the newer version of software runs through a rigorous test, something like 200 gigabytes of data runs through and checked everything is still working. So the basic principle is we don't allow any version of the software to be delivered to customer without testing Docker. Let's say this container technology in general actually is 100% automating all this process, which actually give us a lot of freedom so we have a rather very small team here at NIH. Many people are actually very impressed by how many customer we support within this so small team. So the key reason is because we have a strongly utilized container technology, so its automation is unparalleled, certainly much better than anything I had before using this container technology. So that's actually the key to maintain the quality and the continuous service to our customers. >> Yeah, absolutely. Automation is something we've been talking about in the industry for a long time but if we implement it properly it can have a huge impact. Can you bring us inside a little bit, you know, what tools are you doing? How is that automation set up and managed? And how that fits into the Docker environment. >> So I kind of describe to be more specific. So we are using a continuous testing framework. There are several apps to be using a specific one to build on, which is an open source Python tool, rather small actually. What it can do is, this tool will set up at the service, then this service will watch for example our GitHub repo. Whenever I make a change or someone in the team makes a change for example, fix a bug, add a new feature, or maybe update a new AI model, we push the edge of the GitHub then there's a continuous building system that will notice, it will trigger the integration test run all inside Docker environment. So this is the key. What container technology offers is that we can have 100% reproducible runtime environment for our customers as the software provider, because in our particular use case we don't set up customer with the uniform hardware so they bought their own server around the world, so everyone may have slightly different hardware. We don't want that to get into our software experience. So Docker actually offers us the 100% control of the runtime environment which is very essential if we want to deliver a consistent medical imaging experience because most applications actually it's rather computational intensive, so they don't want something to run for like one minute in one site and maybe three minutes at another site. So what Docker place is that Docker will run all the integration tests. If everything pass then they pack the Docker image then send to the Docker Hub. Then all our collaborators around the world have new image then they will coordinate with them so they will find a proper time to update then they have the newer technology in time. So that's why Docker is such a useful tool for us. >> Yeah, absolutely. Okay, containerization in Docker really transformed the way a lot of those computational solutions happen. I'm wondering if you can explain a little bit more the stack that you're using if people that might not have looked at solutions for a couple of years think oh it's containers, it's dateless architectures, I'm not sure how it fits into my other network environment. Can you tell us what are you doing for the storage in the network? >> So we actually have a rather vertical integration in this medical imaging application, so we build our own service as the software, its backbone is C++ for the higher computational efficiency. There's lots of Python because these days AI model essential. What Docker provides, as I mentioned, uniform always this runtime environment so we have a fixed GCC version then if we want to go into that detail. Specific version of numerical library, certain versions of Python, will be using PyTorch a lot. So that's our AI backbone. Another way of using Docker is actually we deploy the same container into the Microsoft Azure cloud. That's another ability I found out about Docker, so we never need to change anything in our software development process, but the same container I give you must work everywhere on the cloud, on site, for our customers. This actually reduces the development cost, also improve our efficiency a lot. Another important aspect is this actually will improve customers', how do they say it, customer acceptance a lot because they go to one customer, tell them the software you are running is actually running on 30 other sites exactly the same up to the let's say heights there, so it's bit by bit consistent. This actually help us convince many people. Every time when I describe this process I think most people accept the idea. They actually appreciate the way how we deliver software to them because we always can falling back. So yes, here is another aspect. So we have many Docker images that's in the Docker Hub, so if one deployment fails, they can easily falling back. That's actually very important for medical imaging applications that fail because hospitals need to maintain their continuous level of service. So even we want to avoid this completely but yes occasionally, very occasionally, there will be some function not working or some new test case never covered before, then we give them an magnet then, falling back, that's actually also our policy and offered by the container technology. >> Yeah, absolutely. You brought up, many have said that the container is that atomic unit of building block and that portability around any platform environment. What about container orchestration? How are you managing these environments you talked about in the public cloud or in different environments? What are you doing for container orchestration? >> Actually our set-up might be the simplest case. So we basically have a private Docker repo which we paid, actually the Institute has paid. We have something like 50 or 100 private repos, then for every repo we have one specific Docker setup with different software versions of different, for example some image is for PyTorch another for TensorFlow depending on our application. Maybe some customer has the requirement to have rather small Docker image size then they have some trimmed down version of image. In this process, because it's still in a small number like 20, 30 active repo, we are actually managing it semi-automatically so we have the service running to push and pull, and loading back images but we actually configured this process here at the Institute whenever we feel we have something new to offer to the customer. Regarding managing this Docker image, it's actually another aspect for the medical image. So at the customer side, we had a lot of discussion with them for whether we want to set up a continuous automated app, but in the end they decided, they said they'd better have customers involved. Better have some people. So we were finally stopped there by, we noticed customer, there are something new to update then they will decide when to update, how to test. So this is another aspect. Even we have a very high level of confirmation using the container technology, we found it's not 100%. In some site, it's still better have human supervision to help because if the goal is to maintain 100% continuous service then in the end they need some experts on the field to test and verify. So that's how they are in the current stage of deployment of this Docker image. We found it's rather light-weight so even with a few people at NIH in our team, they can manage a rather large network globally, so it's really exciting for us. >> Excellent. Great. I guess final question, give us a little bit of a road map as to, you've already talked about leveraging AI in there, the various pieces, what are you looking for from Docker in the ecosystem, and your solution for the rest of the year? >> I would say the future definitely is on the cloud. One major direction we are trying to push is to go the clinical hospital, linking and use the cloud in building as a routine. So in current status, some of sites, hospital may be very conservative, they are afraid of the security, the connection, all kinds of issues related to cloud. But this scenario is changing rapidly, especially container technology contributes a lot on the cloud. So it makes the whole thing so easy, so reliable. So our next push is to move in lots of the application into the cloud only. So the model will be, for example, we have new AI applications. It may be only available on the cloud. If some customer is waiting to use them they will have to be willing to connect to the cloud and maybe sending data there and receive, for example, the AI apps from our running Docker image in the cloud, but what we need to do is to make the Docker building even more efficiency. Make the computation 100% stable so we can utilize the huge computational power in the cloud. Also the price, so the key here is the price. So if we have one setup in the cloud, a data center for example, we currently maintain two data centers one across Europe, another is in United States. So if we have one data center and 50 hospitals using it every day, then we need the numbers. The average price for one patient comes to a few dollars per patient. So if we consider this medical health care system the costs, the ideal costs of using cloud computing can be truly trivial, but what we can offer to patients and doctor has never happened. The computation you can bring to us is something they never saw before and they never experienced. So I believe that's the future, it's not, the old model is everyone has his own computational server, then maintaining that, it costs a lot of work. Even doctor make the software aspects much easier, but the hardware, someone still need to set-up them. But using cloud will change all of. So I think the next future is definitely to wholly utilize the cloud with the container technology. >> Excellent. Well, we thank you so much. I know everyone appreciates the work your team's doing and absolutely if things can be done to allow scalability and lower cost per patient that would be a huge benefit. Thank you so much for joining us. >> Thank you. >> All right, stay tuned for lots more coverage from theCUBE at DockerCon Live 2020. I'm Stu Miniman and thank you for watching theCUBE. (gentle music)

>> Announcer: From around the globe, it's the queue with digital coverage of DockerCon live 2020. Brought to you by Docker and its ecosystem partners. >> Welcome, welcome, welcome to DockerCon 2020. We got over 50,000 people registered so there's clearly a ton of interest in the world of Docker and Eddie's as I like to call it. And we've assembled a power panel of Open Source and cloud native experts to talk about where things stand in 2020 and where we're headed. I'm Shawn Conley, I'll be the moderator for today's panel. I'm also a proud alum of JBoss, Red Hat, SpringSource, VMware and Hortonworks and I'm broadcasting from my hometown of Philly. Our panelists include; Michelle Noorali, Senior Software Engineer at Microsoft, joining us from Atlanta, Georgia. We have Kelsey Hightower, Principal developer advocate at Google Cloud, joining us from Washington State and we have Chris Aniszczyk, CTO CIO at the CNCF, joining us from Austin, Texas. So I think we have the country pretty well covered. Thank you all for spending time with us on this power panel. Chris, I'm going to start with you, let's dive right in. You've been in the middle of the Docker netease wave since the beginning with a clear focus on building a better world through open collaboration. What are your thoughts on how the Open Source landscape has evolved over the past few years? Where are we in 2020? And where are we headed from both community and a tech perspective? Just curious to get things sized up? >> Sure, when CNCF started about roughly four, over four years ago, the technology mostly focused on just the things around Kubernetes, monitoring communities with technology like Prometheus, and I think in 2020 and the future, we definitely want to move up the stack. So there's a lot of tools being built on the periphery now. So there's a lot of tools that handle running different types of workloads on Kubernetes. So things like Uvert and Shay runs VMs on Kubernetes, which is crazy, not just containers. You have folks that, Microsoft experimenting with a project called Kruslet which is trying to run web assembly workloads natively on Kubernetes. So I think what we've seen now is more and more tools built around the periphery, while the core of Kubernetes has stabilized. So different technologies and spaces such as security and different ways to run different types of workloads. And at least that's kind of what I've seen. >> So do you have a fair amount of vendors as well as end users still submitting in projects in, is there still a pretty high volume? >> Yeah, we have 48 total projects in CNCF right now and Michelle could speak a little bit more to this being on the DOC, the pipeline for new projects is quite extensive and it covers all sorts of spaces from two service meshes to security projects and so on. So it's ever so expanding and filling in gaps in that cloud native landscape that we have. >> Awesome. Michelle, Let's head to you. But before we actually dive in, let's talk a little glory days. A rumor has it that you are the Fifth Grade Kickball Championship team captain. (Michelle laughs) Are the rumors true? >> They are, my speech at the end of the year was the first talk I ever gave. But yeah, it was really fun. I wasn't captain 'cause I wasn't really great at anything else apart from constantly cheer on the team. >> A little better than my eighth grade Spelling Champ Award so I think I'd rather have the kickball. But you've definitely, spent a lot of time leading an Open Source, you've been across many projects for many years. So how does the art and science of collaboration, inclusivity and teamwork vary? 'Cause you're involved in a variety of efforts, both in the CNCF and even outside of that. And then what are some tips for expanding the tent of Open Source projects? >> That's a good question. I think it's about transparency. Just come in and tell people what you really need to do and clearly articulate your problem, more clearly articulate your problem and why you can't solve it with any other solution, the more people are going to understand what you're trying to do and be able to collaborate with you better. What I love about Open Source is that where I've seen it succeed is where incentives of different perspectives and parties align and you're just transparent about what you want. So you can collaborate where it makes sense, even if you compete as a company with another company in the same area. So I really like that, but I just feel like transparency and honesty is what it comes down to and clearly communicating those objectives. >> Yeah, and the various foundations, I think one of the things that I've seen, particularly Apache Software Foundation and others is the notion of checking your badge at the door. Because the competition might be between companies, but in many respects, you have engineers across many companies that are just kicking butt with the tech they contribute, claiming victory in one way or the other might make for interesting marketing drama. But, I think that's a little bit of the challenge. In some of the, standards-based work you're doing I know with CNI and some other things, are they similar, are they different? How would you compare and contrast into something a little more structured like CNCF? >> Yeah, so most of what I do is in the CNCF, but there's specs and there's projects. I think what CNCF does a great job at is just iterating to make it an easier place for developers to collaborate. You can ask the CNCF for basically whatever you need, and they'll try their best to figure out how to make it happen. And we just continue to work on making the processes are clearer and more transparent. And I think in terms of specs and projects, those are such different collaboration environments. Because if you're in a project, you have to say, "Okay, I want this feature or I want this bug fixed." But when you're in a spec environment, you have to think a little outside of the box and like, what framework do you want to work in? You have to think a little farther ahead in terms of is this solution or this decision we're going to make going to last for the next how many years? You have to get more of a buy in from all of the key stakeholders and maintainers. So it's a little bit of a longer process, I think. But what's so beautiful is that you have this really solid, standard or interface that opens up an ecosystem and allows people to build things that you could never have even imagined or dreamed of so-- >> Gotcha. So I'm Kelsey, we'll head over to you as your focus is on, developer advocate, you've been in the cloud native front lines for many years. Today developers are faced with a ton of moving parts, spanning containers, functions, Cloud Service primitives, including container services, server-less platforms, lots more, right? I mean, there's just a ton of choice. How do you help developers maintain a minimalist mantra in the face of such a wealth of choice? I think minimalism I hear you talk about that periodically, I know you're a fan of that. How do you pass that on and your developer advocacy in your day to day work? >> Yeah, I think, for most developers, most of this is not really the top of mind for them, is something you may see a post on Hacker News, and you might double click into it. Maybe someone on your team brought one of these tools in and maybe it leaks up into your workflow so you're forced to think about it. But for most developers, they just really want to continue writing code like they've been doing. And the best of these projects they'll never see. They just work, they get out of the way, they help them with log in, they help them run their application. But for most people, this isn't the core idea of the job for them. For people in operations, on the other hand, maybe these components fill a gap. So they look at a lot of this stuff that you see in the CNCF and Open Source space as number one, various companies or teams sharing the way that they do things, right? So these are ideas that are put into the Open Source, some of them will turn into products, some of them will just stay as projects that had mutual benefit for multiple people. But for the most part, it's like walking through an ion like Home Depot. You pick the tools that you need, you can safely ignore the ones you don't need, and maybe something looks interesting and maybe you study it to see if that if you have a problem. And for most people, if you don't have that problem that that tool solves, you should be happy. No one needs every project and I think that's where the foundation for confusion. So my main job is to help people not get stuck and confused in LAN and just be pragmatic and just use the tools that work for 'em. >> Yeah, and you've spent the last little while in the server-less space really diving into that area, compare and contrast, I guess, what you found there, minimalist approach, who are you speaking to from a server-less perspective versus that of the broader CNCF? >> The thing that really pushed me over, I was teaching my daughter how to make a website. So she's on her Chromebook, making a website, and she's hitting 127.0.0.1, and it looks like geo cities from the 90s but look, she's making website. And she wanted her friends to take a look. So she copied and paste from her browser 127.0.0.1 and none of her friends could pull it up. So this is the point where every parent has to cross that line and say, "Hey, do I really need to sit down "and teach my daughter about Linux "and Docker and Kubernetes." That isn't her main goal, her goal was to just launch her website in a way that someone else can see it. So we got Firebase installed on her laptop, she ran one command, Firebase deploy. And our site was up in a few minutes, and she sent it over to her friend and there you go, she was off and running. The whole server-less movement has that philosophy as one of the stated goal that needs to be the workflow. So, I think server-less is starting to get closer and closer, you start to see us talk about and Chris mentioned this earlier, we're moving up the stack. Where we're going to up the stack, the North Star there is feel where you get the focus on what you're doing, and not necessarily how to do it underneath. And I think server-less is not quite there yet but every type of workload, stateless web apps check, event driven workflows check, but not necessarily for things like machine learning and some other workloads that more traditional enterprises want to run so there's still work to do there. So server-less for me, serves as the North Star for why all these Projects exists for people that may have to roll their own platform, to provide the experience. >> So, Chris, on a related note, with what we were just talking about with Kelsey, what's your perspective on the explosion of the cloud native landscape? There's, a ton of individual projects, each can be used separately, but in many cases, they're like Lego blocks and used together. So things like the surface mesh interface, standardizing interfaces, so things can snap together more easily, I think, are some of the approaches but are you doing anything specifically to encourage this cross fertilization and collaboration of bug ability, because there's just a ton of projects, not only at the CNCF but outside the CNCF that need to plug in? >> Yeah, I mean, a lot of this happens organically. CNCF really provides of the neutral home where companies, competitors, could trust each other to build interesting technology. We don't force integration or collaboration, it happens on its own. We essentially allow the market to decide what a successful project is long term or what an integration is. We have a great Technical Oversight Committee that helps shepherd the overall technical vision for the organization and sometimes steps in and tries to do the right thing when it comes to potentially integrating a project. Previously, we had this issue where there was a project called Open Tracing, and an effort called Open Census, which is basically trying to standardize how you're going to deal with metrics, on the tree and so on in a cloud native world that we're essentially competing with each other. The CNCF TC and committee came together and merged those projects into one parent ever called Open Elementary and so that to me is a case study of how our committee helps, bridges things. But we don't force things, we essentially want our community of end users and vendors to decide which technology is best in the long term, and we'll support that. >> Okay, awesome. And, Michelle, you've been focused on making distributed systems digestible, which to me is about simplifying things. And so back when Docker arrived on the scene, some people referred to it as developer dopamine, which I love that term, because it's simplified a bunch of crufty stuff for developers and actually helped them focus on doing their job, writing code, delivering code, what's happening in the community to help developers wire together multi-part modern apps in a way that's elegant, digestible, feels like a dopamine rush? >> Yeah, one of the goals of the(mumbles) project was to make it easier to deploy an application on Kubernetes so that you could see what the finished product looks like. And then dig into all of the things that that application is composed of, all the resources. So we're really passionate about this kind of stuff for a while now. And I love seeing projects that come into the space that have this same goal and just iterate and make things easier. I think we have a ways to go still, I think a lot of the iOS developers and JS developers I get to talk to don't really care that much about Kubernetes. They just want to, like Kelsey said, just focus on their code. So one of the projects that I really like working with is Tilt gives you this dashboard in your CLI, aggregates all your logs from your applications, And it kind of watches your application changes, and reconfigures those changes in Kubernetes so you can see what's going on, it'll catch errors, anything with a dashboard I love these days. So Yali is like a metrics dashboard that's integrated with STL, a service graph of your service mesh, and lets you see the metrics running there. I love that, I love that dashboard so much. Linkerd has some really good service graph images, too. So anything that helps me as an end user, which I'm not technically an end user, but me as a person who's just trying to get stuff up and running and working, see the state of the world easily and digest them has been really exciting to see. And I'm seeing more and more dashboards come to light and I'm very excited about that. >> Yeah, as part of the DockerCon just as a person who will be attending some of the sessions, I'm really looking forward to see where DockerCompose is going, I know they opened up the spec to broader input. I think your point, the good one, is there's a bit more work to really embrace the wealth of application artifacts that compose a larger application. So there's definitely work the broader community needs to lean in on, I think. >> I'm glad you brought that up, actually. Compose is something that I should have mentioned and I'm glad you bring that up. I want to see programming language libraries, integrate with the Compose spec. I really want to see what happens with that I think is great that they open that up and made that a spec because obviously people really like using Compose. >> Excellent. So Kelsey, I'd be remiss if I didn't touch on your January post on changelog entitled, "Monoliths are the Future." Your post actually really resonated with me. My son works for a software company in Austin, Texas. So your hometown there, Chris. >> Yeah. >> Shout out to Will and the chorus team. His development work focuses on adding modern features via micro services as extensions to the core monolith that the company was founded on. So just share some thoughts on monoliths, micro services. And also, what's deliverance dopamine from your perspective more broadly, but people usually phrase as monoliths versus micro services, but I get the sense you don't believe it's either or. >> Yeah, I think most companies from the pragmatic so one of their argument is one of pragmatism. Most companies have trouble designing any app, monolith, deployable or microservices architecture. And then these things evolve over time. Unless you're really careful, it's really hard to know how to slice these things. So taking an idea or a problem and just knowing how to perfectly compartmentalize it into individual deployable component, that's hard for even the best people to do. And double down knowing the actual solution to the particular problem. A lot of problems people are solving they're solving for the first time. It's really interesting, our industry in general, a lot of people who work in it have never solved the particular problem that they're trying to solve for the first time. So that's interesting. The other part there is that most of these tools that are here to help are really only at the infrastructure layer. We're talking freeways and bridges and toll bridges, but there's nothing that happens in the actual developer space right there in memory. So the libraries that interface to the structure logging, the libraries that deal with rate limiting, the libraries that deal with authorization, can this person make this query with this user ID? A lot of those things are still left for developers to figure out on their own. So while we have things like the brunettes and fluid D, we have all of these tools to deploy apps into those target, most developers still have the problem of everything you do above that line. And to be honest, the majority of the complexity has to be resolved right there in the app. That's the thing that's taking requests directly from the user. And this is where maybe as an industry, we're over-correcting. So we had, you said you come from the JBoss world, I started a lot of my Cisco administration, there's where we focus a little bit more on the actual application needs, maybe from a router that as well. But now what we're seeing is things like Spring Boot, start to offer a little bit more integration points in the application space itself. So I think the biggest parts that are missing now are what are the frameworks people will use for authorization? So you have projects like OPA, Open Policy Agent for those that are new to that, it gives you this very low level framework, but you still have to understand the concepts around, what does it mean to allow someone to do something and one missed configuration, all your security goes out of the window. So I think for most developers this is where the next set of challenges lie, if not actually the original challenge. So for some people, they were able to solve most of these problems with virtualization, run some scripts, virtualize everything and be fine. And monoliths were okay for that. For some reason, we've thrown pragmatism out of the window and some people are saying the only way to solve these problems is by breaking the app into 1000 pieces. Forget the fact that you had trouble managing one piece, you're going to somehow find the ability to manage 1000 pieces with these tools underneath but still not solving the actual developer problems. So this is where you've seen it already with a couple of popular blog posts from other companies. They cut too deep. They're going from 2000, 3000 microservices back to maybe 100 or 200. So to my world, it's going to be not just one monolith, but end up maybe having 10 or 20 monoliths that maybe reflect the organization that you have versus the architectural pattern that you're at. >> I view it as like a constellation of stars and planets, et cetera. Where you you might have a star that has a variety of, which is a monolith, and you have a variety of sort of planetary microservices that float around it. But that's reality, that's the reality of modern applications, particularly if you're not starting from a clean slate. I mean your points, a good one is, in many respects, I think the infrastructure is code movement has helped automate a bit of the deployment of the platform. I've been personally focused on app development JBoss as well as springsSource. The Spring team I know that tech pretty well over the years 'cause I was involved with that. So I find that James Governor's discussion of progressive delivery really resonates with me, as a developer, not so much as an infrastructure Deployer. So continuous delivery is more of infrastructure notice notion, progressive delivery, feature flags, those types of things, or app level, concepts, minimizing the blast radius of your, the new features you're deploying, that type of stuff, I think begins to speak to the pain of application delivery. So I'll guess I'll put this up. Michelle, I might aim it to you, and then we'll go around the horn, what are your thoughts on the progressive delivery area? How could that potentially begin to impact cloud native over 2020? I'm looking for some rallying cries that move up the stack and give a set of best practices, if you will. And I think James Governor of RedMonk opened on something that's pretty important. >> Yeah, I think it's all about automating all that stuff that you don't really know about. Like Flagger is an awesome progressive delivery tool, you can just deploy something, and people have been asking for so many years, ever since I've been in this space, it's like, "How do I do AB deployment?" "How do I do Canary?" "How do I execute these different deployment strategies?" And Flagger is a really good example, for example, it's a really good way to execute these deployment strategies but then, make sure that everything's happening correctly via observing metrics, rollback if you need to, so you don't just throw your whole system. I think it solves the problem and allows you to take risks but also keeps you safe in that you can be confident as you roll out your changes that it all works, it's metrics driven. So I'm just really looking forward to seeing more tools like that. And dashboards, enable that kind of functionality. >> Chris, what are your thoughts in that progressive delivery area? >> I mean, CNCF alone has a lot of projects in that space, things like Argo that are tackling it. But I want to go back a little bit to your point around developer dopamine, as someone that probably spent about a decade of his career focused on developer tooling and in fact, if you remember the Eclipse IDE and that whole integrated experience, I was blown away recently by a demo from GitHub. They have something called code spaces, which a long time ago, I was trying to build development environments that essentially if you were an engineer that joined a team recently, you could basically get an environment quickly start it with everything configured, source code checked out, environment properly set up. And that was a very hard problem. This was like before container days and so on and to see something like code spaces where you'd go to a repo or project, open it up, behind the scenes they have a container that is set up for the environment that you need to build and just have a VS code ID integrated experience, to me is completely magical. It hits like developer dopamine immediately for me, 'cause a lot of problems when you're going to work with a project attribute, that whole initial bootstrap of, "Oh you need to make sure you have this library, this install," it's so incredibly painful on top of just setting up your developer environment. So as we continue to move up the stack, I think you're going to see an incredible amount of improvements around the developer tooling and developer experience that people have powered by a lot of this cloud native technology behind the scenes that people may not know about. >> Yeah, 'cause I've been talking with the team over at Docker, the work they're doing with that desktop, enable the aim local environment, make sure it matches as closely as possible as your deployed environments that you might be targeting. These are some of the pains, that I see. It's hard for developers to get bootstrapped up, it might take him a day or two to actually just set up their local laptop and development environment, and particularly if they change teams. So that complexity really corralling that down and not necessarily being overly prescriptive as to what tool you use. So if you're visual code, great, it should feel integrated into that environment, use a different environment or if you feel more comfortable at the command line, you should be able to opt into that. That's some of the stuff I get excited to potentially see over 2020 as things progress up the stack, as you said. So, Michelle, just from an innovation train perspective, and we've covered a little bit, what's the best way for people to get started? I think Kelsey covered a little bit of that, being very pragmatic, but all this innovation is pretty intimidating, you can get mowed over by the train, so to speak. So what's your advice for how people get started, how they get involved, et cetera. >> Yeah, it really depends on what you're looking for and what you want to learn. So, if you're someone who's new to the space, honestly, check out the case studies on cncf.io, those are incredible. You might find environments that are similar to your organization's environments, and read about what worked for them, how they set things up, any hiccups they crossed. It'll give you a broad overview of the challenges that people are trying to solve with the technology in this space. And you can use that drill into the areas that you want to learn more about, just depending on where you're coming from. I find myself watching old KubeCon talks on the cloud native computing foundations YouTube channel, so they have like playlists for all of the conferences and the special interest groups in CNCF. And I really enjoy talking, I really enjoy watching excuse me, older talks, just because they explain why things were done, the way they were done, and that helps me build the tools I built. And if you're looking to get involved, if you're building projects or tools or specs and want to contribute, we have special interest groups in the CNCF. So you can find that in the CNCF Technical Oversight Committee, TOC GitHub repo. And so for that, if you want to get involved there, choose a vertical. Do you want to learn about observability? Do you want to drill into networking? Do you care about how to deliver your app? So we have a cig called app delivery, there's a cig for each major vertical, and you can go there to see what is happening on the edge. Really, these are conversations about, okay, what's working, what's not working and what are the next changes we want to see in the next months. So if you want that kind of granularity and discussion on what's happening like that, then definitely join those those meetings. Check out those meeting notes and recordings. >> Gotcha. So on Kelsey, as you look at 2020 and beyond, I know, you've been really involved in some of the earlier emerging tech spaces, what gets you excited when you look forward? What gets your own level of dopamine up versus the broader community? What do you see coming that we should start thinking about now? >> I don't think any of the raw technology pieces get me super excited anymore. Like, I've seen the circle of around three or four times, in five years, there's going to be a new thing, there might be a new foundation, there'll be a new set of conferences, and we'll all rally up and probably do this again. So what's interesting now is what people are actually using the technology for. Some people are launching new things that maybe weren't possible because infrastructure costs were too high. People able to jump into new business segments. You start to see these channels on YouTube where everyone can buy a mic and a B app and have their own podcasts and be broadcast to the globe, just for a few bucks, if not for free. Those revolutionary things are the big deal and they're hard to come by. So I think we've done a good job democratizing these ideas, distributed systems, one company got really good at packaging applications to share with each other, I think that's great, and never going to reset again. And now what's going to be interesting is, what will people build with this stuff? If we end up building the same things we were building before, and then we're talking about another digital transformation 10 years from now because it's going to be funny but Kubernetes will be the new legacy. It's going to be the things that, "Oh, man, I got stuck in this Kubernetes thing," and there'll be some governor on TV, looking for old school Kubernetes engineers to migrate them to some new thing, that's going to happen. You got to know that. So at some point merry go round will stop. And we're going to be focused on what you do with this. So the internet is there, most people have no idea of the complexities of underwater sea cables. It's beyond one or two people, or even one or two companies to comprehend. You're at the point now, where most people that jump on the internet are talking about what you do with the internet. You can have Netflix, you can do meetings like this one, it's about what you do with it. So that's going to be interesting. And we're just not there yet with tech, tech is so, infrastructure stuff. We're so in the weeds, that most people almost burn out what's just getting to the point where you can start to look at what you do with this stuff. So that's what I keep in my eye on, is when do we get to the point when people just ship things and build things? And I think the closest I've seen so far is in the mobile space. If you're iOS developer, Android developer, you use the SDK that they gave you, every year there's some new device that enables some new things speech to text, VR, AR and you import an STK, and it just worked. And you can put it in one place and 100 million people can download it at the same time with no DevOps team, that's amazing. When can we do that for server side applications? That's going to be something I'm going to find really innovative. >> Excellent. Yeah, I mean, I could definitely relate. I was Hortonworks in 2011, so, Hadoop, in many respects, was sort of the precursor to the Kubernetes area, in that it was, as I like to refer to, it was a bunch of animals in the zoo, wasn't just the yellow elephant. And when things mature beyond it's basically talking about what kind of analytics are driving, what type of machine learning algorithms and applications are they delivering? You know that's when things tip over into a real solution space. So I definitely see that. I think the other cool thing even just outside of the container and container space, is there's just such a wealth of data related services. And I think how those two worlds come together, you brought up the fact that, in many respects, server-less is great, it's stateless, but there's just a ton of stateful patterns out there that I think also need to be addressed as these richer applications to be from a data processing and actionable insights perspective. >> I also want to be clear on one thing. So some people confuse two things here, what Michelle said earlier about, for the first time, a whole group of people get to learn about distributed systems and things that were reserved to white papers, PhDs, CF site, this stuff is now super accessible. You go to the CNCF site, all the things that you read about or we used to read about, you can actually download, see how it's implemented and actually change how it work. That is something we should never say is a waste of time. Learning is always good because someone has to build these type of systems and whether they sell it under the guise of server-less or not, this will always be important. Now the other side of this is, that there are people who are not looking to learn that stuff, the majority of the world isn't looking. And in parallel, we should also make this accessible, which should enable people that don't need to learn all of that before they can be productive. So that's two sides of the argument that can be true at the same time, a lot of people get caught up. And everything should just be server-less and everyone learning about distributed systems, and contributing and collaborating is wasting time. We can't have a world where there's only one or two companies providing all infrastructure for everyone else, and then it's a black box. We don't need that. So we need to do both of these things in parallel so I just want to make sure I'm clear that it's not one of these or the other. >> Yeah, makes sense, makes sense. So we'll just hit the final topic. Chris, I think I'll ask you to help close this out. COVID-19 clearly has changed how people work and collaborate. I figured we'd end on how do you see, so DockerCon is going to virtual events, inherently the Open Source community is distributed and is used to not face to face collaboration. But there's a lot of value that comes together by assembling a tent where people can meet, what's the best way? How do you see things playing out? What's the best way for this to evolve in the face of the new normal? >> I think in the short term, you're definitely going to see a lot of virtual events cropping up all over the place. Different themes, verticals, I've already attended a handful of virtual events the last few weeks from Red Hat summit to Open Compute summit to Cloud Native summit, you'll see more and more of these. I think, in the long term, once the world either get past COVID or there's a vaccine or something, I think the innate nature for people to want to get together and meet face to face and deal with all the serendipitous activities you would see in a conference will come back, but I think virtual events will augment these things in the short term. One benefit we've seen, like you mentioned before, DockerCon, can have 50,000 people at it. I don't remember what the last physical DockerCon had but that's definitely an order of magnitude more. So being able to do these virtual events to augment potential of physical events in the future so you can build a more inclusive community so people who cannot travel to your event or weren't lucky enough to win a scholarship could still somehow interact during the course of event to me is awesome and I hope something that we take away when we start all doing these virtual events when we get back to physical events, we find a way to ensure that these things are inclusive for everyone and not just folks that can physically make it there. So those are my thoughts on on the topic. And I wish you the best of luck planning of DockerCon and so on. So I'm excited to see how it turns out. 50,000 is a lot of people and that just terrifies me from a cloud native coupon point of view, because we'll probably be somewhere. >> Yeah, get ready. Excellent, all right. So that is a wrap on the DockerCon 2020 Open Source Power Panel. I think we covered a ton of ground. I'd like to thank Chris, Kelsey and Michelle, for sharing their perspectives on this continuing wave of Docker and cloud native innovation. I'd like to thank the DockerCon attendees for tuning in. And I hope everybody enjoys the rest of the conference. (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. >> Hi, I'm Stu Miniman and this is theCUBE's coverage of DockerCon LIVE 2020. Happy to welcome back to the program one of our CUBE alumni, Deepak Singh. He's the vice president of compute services at Amazon Web Services. Deepak, great to see you. >> Likewise, hi, Stu. Nice to meet you again. >> All right, so for our audience that hasn't been in your previous times on theCUBE, give us a little bit about, you know, your role and your organization inside AWS? >> Yeah, so I'm, I've been part of the AWS compute services world from, for the last 12 years in various capacities. Today, I run a number of teams, all our container services, our Linux teams, I also happen to run a high performance computing organization, so it's a nice mix of all the computing that our customers do, especially some of the more new and large scale compute types that our customers are doing. >> All right, so Deepak, obviously, you know, the digital events, we understand what's happening with the global pandemic. DockerCon was actually always planned to be an online event but I want to understand, you know, your teams, how things are affecting, we know distributed is something that Amazon's done, but you have to cut up those two pizza and send them out to the additional groups or, you know, what advice are you giving the developers out there? >> Yeah, in many ways, obviously, how we operate has changed. We are at home, maybe I think with our families. DockerCon was always going to be virtual, but many other events like AWS Summits are now virtual so, you know, in some ways, the teams, the people that get most impacted are not necessarily the developers in our team but people who interact a lot with customers, who go to conferences and speak and they are finding new ways of being effective and being successful and they've been very creative at it. Our customers are getting very good at working with us virtually because we can always go to their site, they can always come to Seattle, or run of other sites for meeting. So we've all become very good at, and disciplined at how do you conduct really nice virtual meetings. But from a customer commitment side, from how we are operating, the things that we're doing, not that much has changed. We still run our projects the same way, the teams work together. My team tends to do a lot of happy things like Friday happy hours, they happen to be all virtual. I think last time we played, what word, bingo? I forget exactly what game we played. I know I got some point somewhere. But we do our best to maintain sort of our team chemistry or camaraderie but the mission doesn't change which is our customers expect us to keep operating their services, make sure that they're highly available, keep delivering new capabilities and I think in this environment, in some ways that's even more important than ever, as customer, as the consumer moves online and so much business is being done virtually so it keeps us on our toes but it's been an adjustment but I think we are all, not just us, I think the whole world is doing the best that they can under the circumstances. >> Yeah, absolutely, it definitely has humanized things quite a bit. From a technology standpoint, Deepak, you know, distributed systems has really been the challenge of you know, quite a long journey that people have been going on. Docker has played, you know, a really important role in a lot of these cloud native technologies. It's been just amazing to watch, you know, one of the things I point to in my career is, you know, watching from those very, very early days of Docker to the Cambrian explosion of what we've seen container based services, you know, you've been part of it for quite a number of years and AWS had many services out there. For people that are getting started, you know, what guidance do you give them? What do they understand about, you know, containerization in 2020? >> Yeah, containerization in 2020 is quite a bit different from when Docker started in 2013. I remember speaking at DockerCon, I forget, that's 2014, 2015, and it was a very different world. People are just trying to figure out what containers are that they could package code in deeper. Today, containers are mainstream, it is more customers or at least many customers and they are starting to build new applications, probably starting them either with containers or with some form of server technology. At least that's the default starting point but increasingly, we also seen customers with existing applications starting to think about how do they adapt? And containers are a means to an end. The end is how can we move faster? How can we deliver more quickly? How can our teams be more productive? And how can you do it more, less expensively, at lower cost? And containers are a big part, important and critical piece of that puzzle, both from how customers are operating their infrastructure, that there's a whole ecosystem of schedulers and orchestration and security tools and all the things that an enterprise need to deliver applications using containers that they have built up. Over the last few years, you know, we have multiple container services that meet those needs. And I think that's been the biggest change is that there's so much more. Which also means that when you're getting started, you're faced with many more options. When Docker started, it was this cute whale, Docker run, Docker build Docker push, it was pretty simple, you could get going really quickly. And today you have 500 different options. My guidance to customers really is, boils down to what are you trying to achieve? If you're an organization that's trying to corral infrastructure and trying to use an existing VM more effectively, for example, you probably do want to invest in becoming experts at schedulers and understanding orchestration technologies like ECS and EKS work but if you just want to run applications, you probably want to look at something like Fargate or more. I mean, you could go towards Lambda and just run code. But I think it all boils down to where you're starting your journey. And by the way, understanding Docker run, Docker build and Docker push is still a great idea. It helps you understand how things work. >> All right, so Deepak, you've already brought up a couple of AWS services of, you know, talk about the options out there, that you can either run on top of AWS, you have a lot of native services, you know, ECS, EKS, you mentioned, Fargate there, and very broad ecosystem in space. Could you just, you know, obviously, there are entire breakout sessions to talk about , the various AWS services, but you know, give us that one on one level as to what to understand for container service by AWS. >> Yeah, and these services evolved organically and we launched the Amazon Elastic Container Service or ECS in preview in November or whenever re:Invent was that year in 2014, which seems ages ago in the world of containers but in the end, our goal is to give our customers the most choice, so that they can solve problems the way they want to solve them. So Amazon ECS is our native container orchestration service, it's designed to work with and the rest of the AWS ecosystem. So it uses VPC for networking, it uses IAM identity, it uses ALB for load balancing, other than just good examples, some examples of how it works. But it became pretty clear over time that there was a lot of customers who were investing in communities, very often starting in their own data centers. And as they migrated onto the cloud, they wanted to continue using the same tool plane but they also wanted to not have to manage the complexity of communities control planes, upgrades. And they also wanted some of the same integrations that they were getting with ECS and so that's where the Amazon Elastic Kubernetes Service or EKS comes in, which is, okay, we will manage a control plane for you. We will manage upgrades and patches for you. You focus on building your applications in Kubernetes way, so it embraces Kubernetes. It has, invokes with all the Kubernetes tooling and gives you a Kubernetes native experience, but then also ties into the broad AWS ecosystem and allows us to take care of some of the muck that many customers quite frankly don't and shouldn't have to worry about. But then we took it one step further and actually launched the same time as EKS and that's, AWS Fargate, and Fargate was, came from the recognition that we had, actually, a long time ago, which is, one of the beauties of EC2 was that customers never had, had to stop, didn't have to worry about racking and stacking and where a server was running anymore. And the idea was, how can we apply that to the world of containers. And we also learned a little bit from what we had done with Lambda. And we took that and took the server layer and took it out of the way. Then from a customer standpoint, all you're launching is a pod or a task or a service and you're not worrying about which machines I need to get, what types of machines I need to get. And the operational simplicity that comes with it is quite remarkable and quite finding not that, surprisingly, our customers want us to keep pushing the boundary of the kind operational simplicity we can give them but Fargate serves a critical building block and part of that, and we're super excited because, you know, today by far when a new customer, when a customer comes and runs a container on AWS the first time they pick Fargate, we're usually using ECS because EKS and Fargate is much newer, but that is a default starting point for any new container customer on AWS which is great. >> All right, well, you know, Docker, the company really helped a lot with that democratization, container technologies, you know, all those services that you talked about from AWS. I'm curious now, the partnership with Docker here, you know, how do some of the AWS services, you know, fit in with Docker? I'm thinking Docker Desktop probably someplace that they're, you know, or some connection? >> Yeah, I think one of the things that Docker has always been really good at as a company, as a project, is understanding the developer and the fact that they start off on a laptop. That's where the original Docker experience that go well, and Docker Desktop since then and we see a ton of Docker Desktop customers have used AWS. We also learned very early on, because originally ECS CLI supported Docker Compose. That ecosystem is also very rich and people like building Docker files and post files and just being able to launch them. So we continue to learn from what Docker is doing with Docker Desktop. We continue working with them on making sure that customizing the Docker Compose and Docker Desktop can run all their services and application on AWS. And we'll continue working with Docker, the company, on how we make that a lot easier for our customers, they are our mutual customers, and how we can learn from their simplicity that Docker, the simplicity that Docker brings and the sort of ease of use the Docker bring for the developer and the developer experience. We learn from that for our own services and we love working with them to make sure that the customer that's starting with Docker Desktop or the Docker CLI has a great experience as they move towards a fully orchestrated experience in the cloud, for example. There's a couple of other areas where Docker has turned out to have had foresight and driven some of our thinking. So a few years ago, Docker released this thing called containerd, where they took out their container runtime from inside the bigger Docker engine. And containerd has become a very important project for us as well as, it's the underpinning of Fargate now and we see a lot of interest from customers that want to keep building on containerd as well. And it's going to be very interesting to see how we work with Docker going forward and how we can continue to give our customers a lot of value, starting from the laptop and then ending up with large scale services in the cloud. >> Very interesting stuff, you know, interesting. Anytime we have a conversation about Docker, there's Docker the technology and Docker the company and that leads us down the discussion of open-source technologies . You were just talking about, you know, containerd believe that connects us to Firecracker. What you and your team are involved in, what's your viewpoint is the, you know, what you're seeing from open-source, how does Amazon think of that? And what else can you share with the audience on this topic? >> Yeah, as you've probably seen over the last few years, both from our work in Kubernetes, with things like Firecracker and more recently Bottlerocket. AWS gets deeply involved with open-source in a number of ways. We are involved heavily with a number of CNCF projects, whether it be containerd, whether it be things like Kubernetes itself, projects in the Kubernetes ecosystem, the service mesh world with Envoy and with the containerd project. So where containerd fits in really well with AWS is in a project that we call firecracker-containerd. They're effectively for Fargate, firecracker-containerd as we move Fargate towards Firecracker becomes out of the container in which you run containerd. It's effectively the equivalent of runC in a traditional Docker engine world. And, you know, one of the first things we did when Firecracker got rolled out was open-source the firecracker-containerd project. It's a go project and the idea was it's a great way for people to build VM like isolation and then build sort of these serverless container architectures like we want to do with Fargate. And, you know, I think Firecracker itself has been a great success. You see customer, you know, companies like Libvirt integrating with Firecracker. I've seen a few other examples of, sometimes unbeknownst to us, of people picking a Firecracker and using it for very, very interesting use cases and not just on AWS in other places as well. And we learnt a lot from that that's kind of why Bottlerocket is, was released the way it was. It is both a product and a project. Bottlerocket, the operating system is an open-source project. It's on GitHub, it has all the building tooling, you can take it and do whatever you want with it. And then on the AWS side, we will build and publish Bottlerocket armies, Amazon machine images, we will support them on AWS and there it's a product. But then Bottlerocket the project is something that anybody in the world who wants to run a minimal operating system can choose to pick up. And I think we've learnt a lot from these experiences, how we deal with the community, how we work with other people who are interested in contributing. And you know, Docker is one of the, the Docker open-source pieces and Docker the company are both part of the growing open-source ecosystem that's coming from AWS, especially on the container world. So it's going to be very interesting. And I'll end with, containerization has started impacting other parts of AWS, as well as our other services are being built, very often through ECS and EKS, but they're also influencing how we think about what capabilities we need to build into the broader container ecosystem. >> Yeah, Deepak, you know, you mentioned that some of the learnings from Lambda has impacted the services you're doing on the containerization side. You know, we've been watching some of the blurring of the lines between another container world and the containerization world. You know, there's some open-source projects out there, the CNCS working on things, you know, what's the latest, as you see kind of containerization and serverless and you know, where do you see them going forward? >> This is that I say that crystal balls are not my strong suite. But we hear customers, customers often want the best of both world. What we see very often is that customers don't actually choose just Fargate or just Lambda, they'll choose both. Where for different pieces of their architecture, they may pick a different solution. And sometimes that's driven by what they know, sometimes driven by what fits into their need. Some of the lines blur but they're still quite different. Lambda, for example, as a very event driven architecture, it is one process at a time. It has all these event hooks into the rest of AWS that are hard to replicate. And if that's the world you want to live in or benefit from, you're going to use lambda. If you're running long running services or you want a particular size that you don't get in Lambda or you want to take a more traditional application and convert it into a more modern application, chances are you're starting on Fargate but it fits in really well you have an existing operational model that fits into it. So we see applications evolving very interestingly. It's one reason why when we build a service mesh, we thought forward instead. It is almost impossible that we will have a world that's 100% containers, 100% Lambda or 100% EC2. It's going to be some mix of all of these. We have to think about it that way. And it's something that we constantly think about is how can we do things in a way that companies aren't forced to pick one way to it and "Oh, I'm going to build on Fargate" and then months later, they're like, "Yeah, we should have probably done Lambda." And I think that is something we think a lot about, whether it's from a developer's experience side or if it's from service meshes, which allow you to move back and forth or make the mesh. And I think that is the area where you'll see us do a lot more going forward. >> Excellent, so last last question for you Deepak is just give us a little bit as to what, you know, industry watchers will be looking at the container services going forward, next kind of 12, 18 months? >> Yeah, so I think one of the great things of the last 18 months has been that type of application that we see customers running, I don't think there's any bound to it. We see everything from people running microservices, or whatever you want to call decoupled services these days, but are services in the end, people are running, most are doing a lot of batch processing, machine learning, artificial intelligence that work with containers. But I think where the biggest dangers are going to come is as companies mature, as companies make containers, not just things that they build greenfield applications but also start thinking about migrating legacy applications in much more volume. A few things are going to happen. I think we'll be, containers come with a lot of complexity right now. I think you've, if you've seen my last two talks at re:Invent along with David Richardson from the Lambda team. You'll hear that we talk a lot about the fact that we see, we've made customers think about more things than they used to in the pre container world. I think you'll see now that the early adopter techie part has done, cloud has adopted containers and the next wave of mainstream users is coming in, you'll see more attractions come on as well, you'll see more governance, I think service meshes have a huge role to play here. How identity works or this fits into things like control tower and more sort of enterprise focused tooling around how you put guardrails around your containerized applications. You'll see it two or three different directions, I think you'll see a lot more on the serverless side, just the fact that so many customers start with Fargate, they're going to make us do more. You'll see a lot more on the ease of use developer experience of production side because you started off with the folks who like to tinker and now you're getting more and more customers that just want to run. And then you'll see, and that's actually a place where Docker, the company and the project have a lot to offer, because that's always been different. And then on the other side, you have the governance guardrails, and how is going to be in a compliant environment, how am I going to migrate all these applications over so that work will keep going on and you'll more and more of that. So those are the three buckets I'll use, the world can surprise us and you might end up with something completely radically different but that seems like what we're hearing from our customers right now. >> Excellent, well, Deepak, always a pleasure to catch up with you. Thanks so much for joining us again on theCUBE. >> No, always a pleasure Stu and hopefully, we get to do this again someday in person. >> Absolutely, I'm Stu Miniman, thanks as always for watching theCUBE. >> Deepak: Yep, thank you. (gentle music)

(water running) (upbeat music) (electric buzzing) >> Fuel up! (upbeat music) (audience clapping) (upbeat music) >> Announcer: From around the globe. It's the queue with digital coverage of DockerCon live 2020, brought to you by Docker and its ecosystem partners. >> Hello everyone, welcome to DockerCon 2020. I'm John Furrier with theCUBE I'm in our Palo Alto studios with our quarantine crew. We have a great lineup here for DockerCon 2020. Virtual event, normally it was in person face to face. I'll be with you throughout the day from an amazing lineup of content, over 50 different sessions, cube tracks, keynotes, and we've got two great co-hosts here with Docker, Jenny Burcio and Bret Fisher. We'll be with you all day today, taking you through the program, helping you navigate the sessions. I'm so excited. Jenny, this is a virtual event. We talk about this. Can you believe it? Maybe the internet gods be with us today and hope everyone's having-- >> Yes. >> Easy time getting in. Jenny, Bret, thank you for-- >> Hello. >> Being here. >> Hey. >> Hi everyone, so great to see everyone chatting and telling us where they're from. Welcome to the Docker community. We have a great day planned for you. >> Guys great job getting this all together. I know how hard it is. These virtual events are hard to pull off. I'm blown away by the community at Docker. The amount of sessions that are coming in the sponsor support has been amazing. Just the overall excitement around the brand and the opportunities given this tough times where we're in. It's super exciting again, made the internet gods be with us throughout the day, but there's plenty of content. Bret's got an amazing all day marathon group of people coming in and chatting. Jenny, this has been an amazing journey and it's a great opportunity. Tell us about the virtual event. Why DockerCon virtual. Obviously everyone's canceling their events, but this is special to you guys. Talk about DockerCon virtual this year. >> The Docker community shows up at DockerCon every year, and even though we didn't have the opportunity to do an in person event this year, we didn't want to lose the time that we all come together at DockerCon. The conversations, the amazing content and learning opportunities. So we decided back in December to make DockerCon a virtual event. And of course when we did that, there was no quarantine we didn't expect, you know, I certainly didn't expect to be delivering it from my living room, but we were just, I mean we were completely blown away. There's nearly 70,000 people across the globe that have registered for DockerCon today. And when you look at DockerCon of past right live events, really and we're learning are just the tip of the iceberg and so thrilled to be able to deliver a more inclusive global event today. And we have so much planned I think. Bret, you want to tell us some of the things that you have planned? >> Well, I'm sure I'm going to forget something 'cause there's a lot going on. But, we've obviously got interviews all day today on this channel with John and the crew. Jenny has put together an amazing set of all these speakers, and then you have the captain's on deck, which is essentially the YouTube live hangout where we just basically talk shop. It's all engineers, all day long. Captains and special guests. And we're going to be in chat talking to you about answering your questions. Maybe we'll dig into some stuff based on the problems you're having or the questions you have. Maybe there'll be some random demos, but it's basically not scripted, it's an all day long unscripted event. So I'm sure it's going to be a lot of fun hanging out in there. >> Well guys, I want to just say it's been amazing how you structured this so everyone has a chance to ask questions, whether it's informal laid back in the captain's channel or in the sessions, where the speakers will be there with their presentations. But Jenny, I want to get your thoughts because we have a site out there that's structured a certain way for the folks watching. If you're on your desktop, there's a main stage hero. There's then tracks and Bret's running the captain's tracks. You can click on that link and jump into his session all day long. He's got an amazing set of line of sleet, leaning back, having a good time. And then each of the tracks, you can jump into those sessions. It's on a clock, it'll be available on demand. All that content is available if you're on your desktop. If you're on your mobile, it's the same thing. Look at the calendar, find the session that you want. If you're interested in it, you could watch it live and chat with the participants in real time or watch it on demand. So there's plenty of content to navigate through. We do have it on a clock and we'll be streaming sessions as they happen. So you're in the moment and that's a great time to chat in real time. But there's more, Jenny, getting more out of this event. You guys try to bring together the stimulation of community. How does the participants get more out of the the event besides just consuming some of the content all day today? >> Yes, so first set up your profile, put your picture next to your chat handle and then chat. John said we have various setups today to help you get the most out of your experience are breakout sessions. The content is prerecorded, so you get quality content and the speakers and chat so you can ask questions the whole time. If you're looking for the hallway track, then definitely check out the captain's on deck channel. And then we have some great interviews all day on the queue. So set up your profile, join the conversation and be kind, right? This is a community event. Code of conduct is linked on every page at the top, and just have a great day. >> And Bret, you guys have an amazing lineup on the captain, so you have a great YouTube channel that you have your stream on. So the folks who were familiar with that can get that either on YouTube or on the site. The chat is integrated in, So you're set up, what do you got going on? Give us the highlights. What are you excited about throughout your day? Take us through your program on the captains. That's going to be probably pretty dynamic in the chat too. >> Yeah, so I'm sure we're going to have lots of, stuff going on in chat. So no cLancaerns there about, having crickets in the chat. But we're going to be basically starting the day with two of my good Docker captain friends, (murmurs) and Laura Taco. And we're going to basically start you out and at the end of this keynote, at the end of this hour and we're going to get you going and then you can maybe jump out and go to take some sessions. Maybe there's some stuff you want to check out and other sessions that you want to chat and talk with the instructors, the speakers there, and then you're going to come back to us, right? Or go over, check out the interviews. So the idea is you're hopping back and forth and throughout the day we're basically changing out every hour. We're not just changing out the guests basically, but we're also changing out the topics that we can cover because different guests will have different expertise. We're going to have some special guests in from Microsoft, talk about some of the cool stuff going on there, and basically it's captains all day long. And if you've been on my YouTube live show you've watched that, you've seen a lot of the guests we have on there. I'm lucky to just hang out with all these really awesome people around the world, so it's going to be fun. >> Awesome and the content again has been preserved. You guys had a great session on call for paper sessions. Jenny, this is good stuff. What other things can people do to make it interesting? Obviously we're looking for suggestions. Feel free to chirp on Twitter about ideas that can be new. But you guys got some surprises. There's some selfies, what else? What's going on? Any secret, surprises throughout the day. >> There are secret surprises throughout the day. You'll need to pay attention to the keynotes. Bret will have giveaways. I know our wonderful sponsors have giveaways planned as well in their sessions. Hopefully right you feel conflicted about what you're going to attend. So do know that everything is recorded and will be available on demand afterwards so you can catch anything that you miss. Most of them will be available right after they stream the initial time. >> All right, great stuff, so they've got the Docker selfie. So the Docker selfies, the hashtag is just DockerCon hashtag DockerCon. If you feel like you want to add some of the hashtag no problem, check out the sessions. You can pop in and out of the captains is kind of the cool kids are going to be hanging out with Bret and then all they'll knowledge and learning. Don't miss the keynote, the keynote should be solid. We've got chain Governor from red monk delivering a keynote. I'll be interviewing him live after his keynote. So stay with us. And again, check out the interactive calendar. All you got to do is look at the calendar and click on the session you want. You'll jump right in. Hop around, give us feedback. We're doing our best. Bret, any final thoughts on what you want to share to the community around, what you got going on the virtual event, just random thoughts? >> Yeah, so sorry we can't all be together in the same physical place. But the coolest thing about as business online, is that we actually get to involve everyone, so as long as you have a computer and internet, you can actually attend DockerCon if you've never been to one before. So we're trying to recreate that experience online. Like Jenny said, the code of conduct is important. So, we're all in this together with the chat, so try to be nice in there. These are all real humans that, have feelings just like me. So let's try to keep it cool. And, over in the Catherine's channel we'll be taking your questions and maybe playing some music, playing some games, giving away some free stuff, while you're, in between sessions learning, oh yeah. >> And I got to say props to your rig. You've got an amazing setup there, Bret. I love what your show, you do. It's really bad ass and kick ass. So great stuff. Jenny sponsors ecosystem response to this event has been phenomenal. The attendance 67,000. We're seeing a surge of people hitting the site now. So if you're not getting in, just, Wade's going, we're going to crank through the queue, but the sponsors on the ecosystem really delivered on the content side and also the sport. You want to share a few shout outs on the sponsors who really kind of helped make this happen. >> Yeah, so definitely make sure you check out the sponsor pages and you go, each page is the actual content that they will be delivering. So they are delivering great content to you. So you can learn and a huge thank you to our platinum and gold authors. >> Awesome, well I got to say, I'm super impressed. I'm looking forward to the Microsoft Amazon sessions, which are going to be good. And there's a couple of great customer sessions there. I tweeted this out last night and let them get you guys' reaction to this because there's been a lot of talk around the COVID crisis that we're in, but there's also a positive upshot to this is Cambridge and explosion of developers that are going to be building new apps. And I said, you know, apps aren't going to just change the world, they're going to save the world. So a lot of the theme here is the impact that developers are having right now in the current situation. If we get the goodness of compose and all the things going on in Docker and the relationships, this real impact happening with the developer community. And it's pretty evident in the program and some of the talks and some of the examples. how containers and microservices are certainly changing the world and helping save the world, your thoughts. >> Like you said, a number of sessions and interviews in the program today that really dive into that. And even particularly around COVID, Clement Beyondo is sharing his company's experience, from being able to continue operations in Italy when they were completely shut down beginning of March. We have also in theCUBE channel several interviews about from the national Institute of health and precision cancer medicine at the end of the day. And you just can really see how containerization and developers are moving in industry and really humanity forward because of what they're able to build and create, with advances in technology. >> Yeah and the first responders and these days is developers. Bret compose is getting a lot of traction on Twitter. I can see some buzz already building up. There's huge traction with compose, just the ease of use and almost a call for arms for integrating into all the system language libraries, I mean, what's going on with compose? I mean, what's the captain say about this? I mean, it seems to be really tracking in terms of demand and interest. >> I think we're over 700,000 composed files on GitHub. So it's definitely beyond just the standard Docker run commands. It's definitely the next tool that people use to run containers. Just by having that we just buy, and that's not even counting. I mean that's just counting the files that are named Docker compose YAML. So I'm sure a lot of you out there have created a YAML file to manage your local containers or even on a server with Docker compose. And the nice thing is is Docker is doubling down on that. So we've gotten some news recently, from them about what they want to do with opening the spec up, getting more companies involved because compose is already gathered so much interest from the community. You know, AWS has importers, there's Kubernetes importers for it. So there's more stuff coming and we might just see something here in a few minutes. >> All right, well let's get into the keynote guys, jump into the keynote. If you missing anything, come back to the stream, check out the sessions, check out the calendar. Let's go, let's have a great time. Have some fun, thanks and enjoy the rest of the day we'll see you soon. (upbeat music) (upbeat music) >> Okay, what is the name of that Whale? >> Molly. >> And what is the name of this Whale? >> Mobby. >> That's right, dad's got to go, thanks bud. >> Bye. >> Bye. Hi, I'm Scott Johnson, CEO of Docker and welcome to DockerCon 2020. This year DockerCon is an all virtual event with more than 60,000 members of the Docker Community joining from around the world. And with the global shelter in place policies, we're excited to offer a unifying, inclusive virtual community event in which anyone and everyone can participate from their home. As a company, Docker has been through a lot of changes since our last DockerCon last year. The most important starting last November, is our refocusing 100% on developers and development teams. As part of that refocusing, one of the big challenges we've been working on, is how to help development teams quickly and efficiently get their app from code to cloud And wouldn't it be cool, if developers could quickly deploy to the cloud right from their local environment with the commands and workflow they already know. We're excited to give you a sneak preview of what we've been working on. And rather than slides, we thought we jumped right into the product. And joining me demonstrate some of these cool new features, is enclave your DACA. One of our engineers here at Docker working on Docker compose. Hello Lanca. >> Hello. >> We're going to show how an application development team collaborates using Docker desktop and Docker hub. And then deploys the app directly from the Docker command line to the clouds in just two commands. A development team would use this to quickly share functional changes of their app with the product management team, with beta testers or other development teams. Let's go ahead and take a look at our app. Now, this is a web app, that randomly pulls words from the database, and assembles them into sentences. You can see it's a pretty typical three tier application with each tier implemented in its own container. We have a front end web service, a middle tier, which implements the logic to randomly pull the words from the database and assemble them and a backend database. And here you can see the database uses the Postgres official image from Docker hub. Now let's first run the app locally using Docker command line and the Docker engine in Docker desktop. We'll do a Doc compose up and you can see that it's pulling the containers from our Docker organization account. Wordsmith, inc. Now that it's up. Let's go ahead and look at local host and we'll confirm that the application is functioning as desired. So there's one sentence, let's pull and now you and you can indeed see that we are pulling random words and assembling into sentences. Now you can also see though that the look and feel is a bit dated. And so Lanca is going to show us how easy it is to make changes and share them with the rest of the team. Lanca, over to you. >> Thank you, so I have, the source code of our application on my machine and I have updated it with the latest team from DockerCon 2020. So before committing the code, I'm going to build the application locally and run it, to verify that indeed the changes are good. So I'm going to build with Docker compose the image for the web service. Now that the image has been built, I'm going to deploy it locally. Wait to compose up. We can now check the dashboard in a Docker desktop that indeed our containers are up and running, and we can access, we can open in the web browser, the end point for the web service. So as we can see, we have the latest changes in for our application. So as you can see, the application has been updated successfully. So now, I'm going to push the image that I have just built to my organization's shared repository on Docker hub. So I can do this with Docker compose push web. Now that the image has been updated in the Docker hub repository, or my teammates can access it and check the changes. >> Excellent, well, thank you Lanca. Now of course, in these times, video conferencing is the new normal, and as great as it is, video conferencing does not allow users to actually test the application. And so, to allow us to have our app be accessible by others outside organizations such as beta testers or others, let's go ahead and deploy to the cloud. >> Sure we, can do this by employing a context. A Docker context, is a mechanism that we can use to target different platforms for deploying containers. The context we hold, information as the endpoint for the platform, and also how to authenticate to it. So I'm going to list the context that I have set locally. As you can see, I'm currently using the default context that is pointing to my local Docker engine. So all the commands that I have issued so far, we're targeting my local engine. Now, in order to deploy the application on a cloud. I have an account in the Azure Cloud, where I have no resource running currently, and I have created for this account, dedicated context that will hold the information on how to connect it to it. So now all I need to do, is to switch to this context, with Docker context use, and the name of my cloud context. So all the commands that I'm going to run, from now on, are going to target the cloud platform. So we can also check very, more simpler, in a simpler way we can check the running containers with Docker PS. So as we see no container is running in my cloud account. Now to deploy the application, all I need to do is to run a Docker compose up. And this will trigger the deployment of my application. >> Thanks Lanca. Now notice that Lanca did not have to move the composed file from Docker desktop to Azure. Notice you have to make any changes to the Docker compose file, and nor did she change any of the containers that she and I were using locally in our local environments. So the same composed file, same images, run locally and upon Azure without changes. While the app is deploying to Azure, let's highlight some of the features in Docker hub that helps teams with remote first collaboration. So first, here's our team's account where it (murmurs) and you can see the updated container sentences web that Lanca just pushed a couple of minutes ago. As far as collaboration, we can add members using their Docker ID or their email, and then we can organize them into different teams depending on their role in the application development process. So and then Lancae they're organized into different teams, we can assign them permissions, so that teams can work in parallel without stepping on each other's changes accidentally. For example, we'll give the engineering team full read, write access, whereas the product management team will go ahead and just give read only access. So this role based access controls, is just one of the many features in Docker hub that allows teams to collaboratively and quickly develop applications. Okay Lanca, how's our app doing? >> Our app has been successfully deployed to the cloud. So, we can easily check either the Azure portal to verify the containers running for it or simpler we can run a Docker PS again to get the list with the containers that have been deployed for it. In the output from the Docker PS, we can see an end point that we can use to access our application in the web browser. So we can see the application running in clouds. It's really up to date and now we can take this particular endpoint and share it within our organization such that anybody can have a look at it. >> That's cool Onka. We showed how we can deploy an app to the cloud in minutes and just two commands, and using commands that Docker users already know, thanks so much. In that sneak preview, you saw a team developing an app collaboratively, with a tool chain that includes Docker desktop and Docker hub. And simply by switching Docker context from their local environment to the cloud, deploy that app to the cloud, to Azure without leaving the command line using Docker commands they already know. And in doing so, really simplifying for development team, getting their app from code to cloud. And just as important, what you did not see, was a lot of complexity. You did not see cloud specific interfaces, user management or security. You did not see us having to provision and configure compute networking and storage resources in the cloud. And you did not see infrastructure specific application changes to either the composed file or the Docker images. And by simplifying a way that complexity, these new features help application DevOps teams, quickly iterate and get their ideas, their apps from code to cloud, and helping development teams, build share and run great applications, is what Docker is all about. A Docker is able to simplify for development teams getting their app from code to cloud quickly as a result of standards, products and ecosystem partners. It starts with open standards for applications and application artifacts, and active open source communities around those standards to ensure portability and choice. Then as you saw in the demo, the Docker experience delivered by Docker desktop and Docker hub, simplifies a team's collaborative development of applications, and together with ecosystem partners provides every stage of an application development tool chain. For example, deploying applications to the cloud in two commands. What you saw on the demo, well that's an extension of our strategic partnership with Microsoft, which we announced yesterday. And you can learn more about our partnership from Amanda Silver from Microsoft later today, right here at DockerCon. Another tool chain stage, the capability to scan applications for security and vulnerabilities, as a result of our partnership with Sneak, which we announced last week. You can learn more about that partnership from Peter McKay, CEO Sneak, again later today, right here at DockerCon. A third example, development team can automate the build of container images upon a simple get push, as a result of Docker hub integrations with GitHub and Alaska and Bitbucket. As a final example of Docker and the ecosystem helping teams quickly build applications, together with our ISV partners. We offer in Docker hub over 500 official and verified publisher images of ready to run Dockerized application components such as databases, load balancers, programming languages, and much more. Of course, none of this happens without people. And I would like to take a moment to thank four groups of people in particular. First, the Docker team, past and present. We've had a challenging 12 months including a restructuring and then a global pandemic, and yet their support for each other, and their passion for the product, this community and our customers has never been stronger. We think our community, Docker wouldn't be Docker without you, and whether you're one of the 50 Docker captains, they're almost 400 meetup organizers, the thousands of contributors and maintainers. Every day you show up, you give back, you teach new support. We thank our users, more than six and a half million developers who have built more than 7 million applications and are then sharing those applications through Docker hub at a rate of more than one and a half billion poles per week. Those apps are then run, are more than 44 million Docker engines. And finally, we thank our customers, the over 18,000 docker subscribers, both individual developers and development teams from startups to large organizations, 60% of which are outside the United States. And they spend every industry vertical, from media, to entertainment to manufacturing. healthcare and much more. Thank you. Now looking forward, given these unprecedented times, we would like to offer a challenge. While it would be easy to feel helpless and miss this global pandemic, the challenge is for us as individuals and as a community to instead see and grasp the tremendous opportunities before us to be forces for good. For starters, look no further than the pandemic itself, in the fight against this global disaster, applications and data are playing a critical role, and the Docker Community quickly recognize this and rose to the challenge. There are over 600 COVID-19 related publicly available projects on Docker hub today, from data processing to genome analytics to data visualization folding at home. The distributed computing project for simulating protein dynamics, is also available on Docker hub, and it uses spirit compute capacity to analyze COVID-19 proteins to aid in the design of new therapies. And right here at DockerCon, you can hear how Clemente Biondo and his company engineering in Gagne area Informatica are using Docker in the fight with COVID-19 in Italy every day. Now, in addition to fighting the pandemic directly, as a community, we also have an opportunity to bridge the disruption the pandemic is wreaking. It's impacting us at work and at home in every country around the world and every aspect of our lives. For example, many of you have a student at home, whose world is going to be very different when they returned to school. As employees, all of us have experienced the stresses from working from home as well as many of the benefits and in fact 75% of us say that going forward, we're going to continue to work from home at least occasionally. And of course one of the biggest disruptions has been job losses, over 35 million in the United States alone. And we know that's affected many of you. And yet your skills are in such demand and so important now more than ever. And that's why here at DockerCon, we want to try to do our part to help, and we're promoting this hashtag on Twitter, hashtag DockerCon jobs, where job seekers and those offering jobs can reach out to one another and connect. Now, pandemics disruption is accelerating the shift of more and more of our time, our priorities, our dollars from offline to online to hybrid, and even online only ways of living. We need to find new ways to collaborate, new approaches to engage customers, new modes for education and much more. And what is going to fill the needs created by this acceleration from offline, online? New applications. And it's this need, this demand for all these new applications that represents a great opportunity for the Docker community of developers. The world needs us, needs you developers now more than ever. So let's seize this moment. Let us in our teams, go build share and run great new applications. Thank you for joining today. And let's have a great DockerCon. >> Okay, welcome back to the DockerCon studio headquarters in your hosts, Jenny Burcio and myself John Furrier. u@farrier on Twitter. If you want to tweet me anything @DockerCon as well, share what you're thinking. Great keynote there from Scott CEO. Jenny, demo DockerCon jobs, some highlights there from Scott. Yeah, I love the intro. It's okay I'm about to do the keynote. The little green room comes on, makes it human. We're all trying to survive-- >> Let me answer the reality of what we are all doing with right now. I had to ask my kids to leave though or they would crash the whole stream but yes, we have a great community, a large community gather gathered here today, and we do want to take the opportunity for those that are looking for jobs, are hiring, to share with the hashtag DockerCon jobs. In addition, we want to support direct health care workers, and Bret Fisher and the captains will be running a all day charity stream on the captain's channel. Go there and you'll get the link to donate to directrelief.org which is a California based nonprofit, delivering and aid and supporting health care workers globally response to the COVID-19 crisis. >> Okay, if you jumping into the stream, I'm John Farrie with Jenny Webby, your hosts all day today throughout DockerCon. It's a packed house of great content. You have a main stream, theCUBE which is the mainstream that we'll be promoting a lot of cube interviews. But check out the 40 plus sessions underneath in the interactive calendar on dockercon.com site. Check it out, they're going to be live on a clock. So if you want to participate in real time in the chat, jump into your session on the track of your choice and participate with the folks in there chatting. If you miss it, it's going to go right on demand right after sort of all content will be immediately be available. So make sure you check it out. Docker selfie is a hashtag. Take a selfie, share it. Docker hashtag Docker jobs. If you're looking for a job or have openings, please share with the community and of course give us feedback on what you can do. We got James Governor, the keynote coming up next. He's with Red monk. Not afraid to share his opinion on open source on what companies should be doing, and also the evolution of this Cambrin explosion of apps that are going to be coming as we come out of this post pandemic world. A lot of people are thinking about this, the crisis and following through. So stay with us for more and more coverage. Jenny, favorite sessions on your mind for people to pay attention to that they should (murmurs)? >> I just want to address a few things that continue to come up in the chat sessions, especially breakout sessions after they play live and the speakers in chat with you, those go on demand, they are recorded, you will be able to access them. Also, if the screen is too small, there is the button to expand full screen, and different quality levels for the video that you can choose on your end. All the breakout sessions also have closed captioning, so please if you would like to read along, turn that on so you can, stay with the sessions. We have some great sessions, kicking off right at 10:00 a.m, getting started with Docker. We have a full track really in the how to enhance on that you should check out devs in action, hear what other people are doing and then of course our sponsors are delivering great content to you all day long. >> Tons of content. It's all available. They'll always be up always on at large scale. Thanks for watching. Now we got James Governor, the keynote. He's with Red Monk, the analyst firm and has been tracking open source for many generations. He's been doing amazing work. Watch his great keynote. I'm going to be interviewing him live right after. So stay with us and enjoy the rest of the day. We'll see you back shortly. (upbeat music) >> Hi, I'm James Governor, one of the co-founders of a company called RedMonk. We're an industry research firm focusing on developer led technology adoption. So that's I guess why Docker invited me to DockerCon 2020 to talk about some trends that we're seeing in the world of work and software development. So Monk Chips, that's who I am. I spent a lot of time on Twitter. It's a great research tool. It's a great way to find out what's going on with keep track of, as I say, there's people that we value so highly software developers, engineers and practitioners. So when I started talking to Docker about this event and it was pre Rhona, should we say, the idea of a crowd wasn't a scary thing, but today you see something like this, it makes you feel uncomfortable. This is not a place that I want to be. I'm pretty sure it's a place you don't want to be. And you know, to that end, I think it's interesting quote by Ellen Powell, she says, "Work from home is now just work" And we're going to see more and more of that. Organizations aren't feeling the same way they did about work before. Who all these people? Who is my cLancaern? So GitHub says has 50 million developers right on its network. Now, one of the things I think is most interesting, it's not that it has 50 million developers. Perhaps that's a proxy for number of developers worldwide. But quite frankly, a lot of those accounts, there's all kinds of people there. They're just Selena's. There are data engineers, there are data scientists, there are product managers, there were tech marketers. It's a big, big community and it goes way beyond just software developers itself. Frankly for me, I'd probably be saying there's more like 20 to 25 million developers worldwide, but GitHub knows a lot about the world of code. So what else do they know? One of the things they know is that world of code software and opensource, is becoming increasingly global. I get so excited about this stuff. The idea that there are these different software communities around the planet where we're seeing massive expansions in terms of things like open source. Great example is Nigeria. So Nigeria more than 200 million people, right? The energy there in terms of events, in terms of learning, in terms of teaching, in terms of the desire to code, the desire to launch businesses, desire to be part of a global software community is just so exciting. And you know, these, this sort of energy is not just in Nigeria, it's in other countries in Africa, it's happening in Egypt. It's happening around the world. This energy is something that's super interesting to me. We need to think about that. We've got global that we need to solve. And software is going to be a big part of that. At the moment, we can talk about other countries, but what about frankly the gender gap, the gender issue that, you know, from 1984 onwards, the number of women taking computer science degrees began to, not track but to create in comparison to what men were doing. The tech industry is way too male focused, there are men that are dominant, it's not welcoming, we haven't found ways to have those pathways and frankly to drive inclusion. And the women I know in tech, have to deal with the massively disproportionate amount of stress and things like online networks. But talking about online networks and talking about a better way of living, I was really excited by get up satellite recently, was a fantastic demo by Alison McMillan and she did a demo of a code spaces. So code spaces is Microsoft online ID, new platform that they've built. And online IDs, we're never quite sure, you know, plenty of people still out there just using the max. But, visual studio code has been a big success. And so this idea of moving to one online IDE, it's been around that for awhile. What they did was just make really tight integration. So you're in your GitHub repo and just be able to create a development environment with effectively one click, getting rid of all of the act shaving, making it super easy. And what I loved was it the demo, what Ali's like, yeah cause this is great. One of my kids are having a nap, I can just start (murmurs) and I don't have to sort out all the rest of it. And to me that was amazing. It was like productivity as inclusion. I'm here was a senior director at GitHub. They're doing this amazing work and then making this clear statement about being a parent. And I think that was fantastic. Because that's what, to me, importantly just working from home, which has been so challenging for so many of us, began to open up new possibilities, and frankly exciting possibilities. So Alley's also got a podcast parent-driven development, which I think is super important. Because this is about men and women rule in this together show parenting is a team sport, same as software development. And the idea that we should be thinking about, how to be more productive, is super important to me. So I want to talk a bit about developer culture and how it led to social media. Because you know, your social media, we're in this ad bomb stage now. It's TikTok, it's like exercise, people doing incredible back flips and stuff like that. Doing a bunch of dancing. We've had the world of sharing cat gifts, Facebook, we sort of see social media is I think a phenomenon in its own right. Whereas the me, I think it's interesting because it's its progenitors, where did it come from? So here's (murmurs) So 1971, one of the features in the emergency management information system, that he built, which it's topical, it was for medical tracking medical information as well, medical emergencies, included a bulletin board system. So that it could keep track of what people were doing on a team and make sure that they were collaborating effectively, boom! That was the start of something big, obviously. Another day I think is worth looking at 1983, Sorania Pullman, spanning tree protocol. So at DEC, they were very good at distributed systems. And the idea was that you can have a distributed system and so much of the internet working that we do today was based on radius work. And then it showed that basically, you could span out a huge network so that everyone could collaborate. That is incredibly exciting in terms of the trends, that I'm talking about. So then let's look at 1988, you've got IRC. IRC what developer has not used IRC, right. Well, I guess maybe some of the other ones might not have. But I don't know if we're post IRC yet, but (murmurs) at a finished university, really nailed it with IRC as a platform that people could communicate effectively with. And then we go into like 1991. So we've had IRC, we've had finished universities, doing a lot of really fantastic work about collaboration. And I don't think it was necessarily an accident that this is where the line is twofold, announced Linux. So Linux was a wonderfully packaged, idea in terms of we're going to take this Unix thing. And when I say package, what a package was the idea that we could collaborate on software. So, it may have just been the work of one person, but clearly what made it important, made it interesting, was finding a social networking pattern, for software development so that everybody could work on something at scale. That was really, I think, fundamental and foundational. Now I think it's important, We're going to talk about Linus, to talk about some things that are not good about software culture, not good about open source culture, not good about hacker culture. And that's where I'm going to talk about code of conduct. We have not been welcoming to new people. We got the acronyms, JFTI, We call people news, that's super unhelpful. We've got to find ways to be more welcoming and more self-sustaining in our communities, because otherwise communities will fail. And I'd like to thank everyone that has a code of conduct and has encouraged others to have codes of conduct. We need to have codes of conduct that are enforced to ensure that we have better diversity at our events. And that's what women, underrepresented minorities, all different kinds of people need to be well looked off to and be in safe and inclusive spaces. And that's the online events. But of course it's also for all of our activities offline. So Linus, as I say, I'm not the most charming of characters at all time, but he has done some amazing technology. So we got to like 2005 the creation of GIT. Not necessarily the distributed version control system that would win. But there was some interesting principles there, and they'd come out of the work that he had done in terms of trying to build and sustain the Linux code base. So it was very much based on experience. He had an itch that he needed to scratch and there was a community that was this building, this thing. So what was going to be the option, came up with Git foundational to another huge wave of social change, frankly get to logical awesome. April 20 April, 2008 GitHub, right? GiHub comes up, they've looked at Git, they've packaged it up, they found a way to make it consumable so the teams could use it and really begin to take advantage of the power of that distributed version control model. Now, ironically enough, of course they centralized the service in doing so. So we have a single point of failure on GitHub. But on the other hand, the notion of the poll request, the primitives that they established and made usable by people, that changed everything in terms of software development. I think another one that I'd really like to look at is Slack. So Slack is a huge success used by all different kinds of businesses. But it began specifically as a pivot from a company called Glitch. It was a game company and they still wanted, a tool internally that was better than IRC. So they built out something that later became Slack. So Slack 2014, is established as a company and basically it was this Slack fit software engineering. The focus on automation, the conversational aspects, the asynchronous aspects. It really pulled things together in a way that was interesting to software developers. And I think we've seen this pattern in the world, frankly, of the last few years. Software developers are influences. So Slack first used by the engineering teams, later used by everybody. And arguably you could say the same thing actually happened with Apple. Apple was mainstreamed by developers adopting that platform. Get to 2013, boom again, Solomon Hikes, Docker, right? So Docker was, I mean containers were not new, they were just super hard to use. People found it difficult technology, it was Easter Terek. It wasn't something that they could fully understand. Solomon did an incredible job of understanding how containers could fit into modern developer workflows. So if we think about immutable images, if we think about the ability to have everything required in the package where you are, it really tied into what people were trying to do with CICD, tied into microservices. And certainly the notion of sort of display usability Docker nailed that, and I guess from this conference, at least the rest is history. So I want to talk a little bit about, scratching the itch. And particularly what has become, I call it the developer authentic. So let's go into dark mode now. I've talked about developers laying out these foundations and frameworks that, the mainstream, frankly now my son, he's 14, he (murmurs) at me if I don't have dark mode on in an application. And it's this notion that developers, they have an aesthetic, it does get adopted I mean it's quite often jokey. One of the things we've seen in the really successful platforms like GitHub, Docker, NPM, let's look at GitHub. Let's look at over that Playfulness. I think was really interesting. And that changes the world of work, right? So we've got the world of work which can be buttoned up, which can be somewhat tight. I think both of those companies were really influential, in thinking that software development, which is a profession, it's also something that can and is fun. And I think about how can we make it more fun? How can we develop better applications together? Takes me to, if we think about Docker talking about build, share and run, for me the key word is share, because development has to be a team sport. It needs to be sharing. It needs to be kind and it needs to bring together people to do more effective work. Because that's what it's all about, doing effective work. If you think about zoom, it's a proxy for collaboration in terms of its value. So we've got all of these airlines and frankly, add up that their share that add up their total value. It's currently less than Zoom. So video conferencing has become so much of how we live now on a consumer basis. But certainly from a business to business perspective. I want to talk about how we live now. I want to think about like, what will come out all of this traumatic and it is incredibly traumatic time? I'd like to say I'm very privileged. I can work from home. So thank you to all the frontline workers that are out there that they're not in that position. But overall what I'm really thinking about, there's some things that will come out of this that will benefit us as a culture. Looking at cities like Paris, Milan, London, New York, putting a new cycling infrastructure, so that people can social distance and travel outside because they don't feel comfortable on public transport. I think sort of amazing widening pavements or we can't do that. All these cities have done it literally overnight. This sort of changes is exciting. And what does come off that like, oh there are some positive aspects of the current issues that we face. So I've got a conference or I've got a community that may and some of those, I've been working on. So Katie from HashiCorp and Carla from container solutions basically about, look, what will the world look like in developer relations? Can we have developer relations without the air miles? 'Cause developer advocates, they do too much travel ends up, you know, burning them out, develop relations. People don't like to say no. They may have bosses that say, you know, I was like, Oh that corporates went great. Now we're going to roll it out worldwide to 47 cities. That's stuff is terrible. It's terrible from a personal perspective, it's really terrible from an environmental perspective. We need to travel less. Virtual events are crushing it. Microsoft just at build, right? Normally that'd be just over 10,000 people, they had 245,000 plus registrations. 40,000 of them in the last day, right? Red Hat summit, 80,000 people, IBM think 90,000 people, GitHub Crushed it as well. Like this is a more inclusive way people can dip in. They can be from all around the world. I mentioned Nigeria and how fantastic it is. Very often Nigerian developers and advocates find it hard to get visas. Why should they be shut out of events? Events are going to start to become remote first because frankly, look at it, if you're turning in those kinds of numbers, and Microsoft was already doing great online events, but they absolutely nailed it. They're going to have to ask some serious questions about why everybody should get back on a plane again. So if you're going to do remote, you've got to be intentional about it. It's one thing I've learned some exciting about GitLab. GitLab's culture is amazing. Everything is documented, everything is public, everything is transparent. Think that really clear and if you look at their principles, everything, you can't have implicit collaboration models. Everything needs to be documented and explicit, so that anyone can work anywhere and they can still be part of the team. Remote first is where we're at now, Coinbase, Shopify, even Barkley says the not going to go back to having everybody in offices in the way they used to. This is a fundamental shift. And I think it's got significant implications for all industries, but definitely for software development. Here's the thing, the last 20 years were about distributed computing, microservices, the cloud, we've got pretty good at that. The next 20 years will be about distributed work. We can't have everybody living in San Francisco and London and Berlin. The talent is distributed, the talent is elsewhere. So how are we going to build tools? Who is going to scratch that itch to build tools to make them more effective? Who's building the next generation of apps, you are, thanks.

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

>> announcer: From around the globe. It's the theCUBE with digital coverage of DockerCon live 2020. Brought to you by Docker and its ecosystem partners. >> Welcome back to theCUBE coverage here at the DockerCon virtual headquarters, anchor desks here in the Palo Alto Studios were quarantined in this virtual event of DockerCon. I'm John Furrier, host along with Jenny Bertuccio, John Kreisa, Peter McKee, other folks who are moderating and weaving in and out of the sessions. But here we have a live sessions with Justin Graham, Vice President of the Products group at Docker. Justin, thanks for coming in DockerCon virtual '20. >> Absolutely, happy to be here from my home office in Seattle, Washington where it is almost sunny. >> You had a great backdrop traveler saying in the chat you got a bandwidth, a lot of bandwidth there. Looking good, some island. What a day for Docker global event. 77,000 people registered. It's just been an awesome party. >> It's been great, I could hardly sleep last night. I was up at 5:00 this morning. I was telling my son about it at breakfast. I interrupted his Zoom school. And he talked a little bit about it, so it's been awesome. I've been waiting for this interview slot for the most of the day. >> So yeah, I got to tell the kids to get off, download those gigabytes of new game updates and get off Netflix, I hear you. But you got good bandwidth. Let's get into it, I love your position. VP of Product at a company that's super technical, a lot of software, a lot of cloud. You've got a good view of the landscape of what the current situation is relative to the product, the deals that are going on with this new announced here, sneak Microsoft expansion, multiple clouds as well as the roadmap and community interaction. So you got a lot going on, you've got your fingers in all the action. When you get the keys to the kingdom, as we say in the product side of things, what's the story today from your perspective around DockerCon? What's the most important thing people should know about of what's going on with this new Docker? Obviously, ease of use, we've heard a lot about. What's going on? >> So I'll start with people. We are hyper focused on helping developers and development teams build and ship applications. That's what we're focused on. That's what we wake up every day thinking about. And we double click on that a minute in terms of what that means. If you think about where source control ends and having a running application on some production compute in the Cloud on the other end, there's a whole lot that needs to happen in the middle of those two things. And we hear from our development community and we see from those folks, there's a lot of complexity and choices and options and things in the middle there. And we really want to help streamline the creation of those pipelines to get those apps moving to production as fastly, as quickly as possible. >> And you can see it in some of the results and some of the sessions, one session coming up at around four, around how pipelining with Docker help increase the problem solving around curing cancer, really solving, saving people's lives to the front lines with COVID 19 to business value. So you seeing, again Docker coming back into the fold relative to the simple value proposition of making things super easy for developers, but on top of the mega trend of microservices. So, outside of some of these awesome sessions with his learning, the hardcore sessions here at DockerCon around microservices from monitoring, you name it, not a trivial thing cause you've got stateless and state, all kinds of new things are going on with multiple clouds. So not an easy-- >> No. >> road to kind of grok or understand you have to manage that. What are people paying attention to? What is happening? I think, first off I'll say, one of the things that I'm super passionate about is increasing access to technology, so the greatest and best ideas can get bubbled up to the top and expose no matter where they come from, whom they come from, et cetera. And I think one of the things that makes that harder, that makes that complex is just how much developers need to understand or even emerging developers need to understand. Just to even get started. Languages, IDEs, packaging, building where do you ship to? If you pick a certain powder end point, you have to understand networking and storage and identity models are just so much you have to absorb. So we're hyper focused on how can we make that complex super easy. And these are all the things that we get asked questions on. And we get interacted with on our public roadmap in other places to help with. So that's the biggest things that you're going to see coming out of Docker starting now and moving forward. We'll be serving that end. >> Let's talk about some of the new execution successes you guys had. Honestly, Snyk is security shifting left, that's a major, I think a killer win for Snyk. Obviously, getting access to millions of developers use Docker and vice versa. Into the shifting left, you get to security in that workflow piece. Microsoft expanding relationship's interesting as well because Microsoft's got a robust tech developer ecosystem. They have their own tools. So, you see these symbiotic relationship with Docker, again, coming into the fold where there's a lot of working together going on. Explain that meaning, what does that mean? >> So you're on the back of the refocus Docker in our hyperfocus on developers and development teams, one of the core tenants of the how. So before that was the what. This is the how we're going to go do it. Is by partnering with the ecosystem as much as possible and bringing the best of breed in front of developers in a way that they can most easily consume. So if you take the Snyk partnership that was just a match, a match made in developer dopamine as a Sean Connolly, would say. We're hyper focused on developers and development teams and Snyk is also hyperfocused on making it as easy as possible for developers and development teams to stay secure ship, fast and stay secure. So it really just matched up super well. And then if you think, "Well, how do we even get there in the first place?" Well, we launched our public roadmap a few months ago, which was a first that Docker has ever done. And one of the first things that comes onto that public roadmap is image vulnerability scanning. For Docker, at that time it was really just focused on Docker Hub in terms of how it came through the roadmap. It got up voted a bunch, there has been some interaction and then we thought, "Well, why just like checking that box isn't enough," right? It's just checking the box. What can we do that really brings sort of the promise of the Docker experience to something like this? And Sneak was an immediate thought, in that respect. And we just really got in touch with them and we just saw eye to eye almost immediately. And then off off the rest went. The second piece of it was really around, well why just do it in Docker Hub? What about Docker Desktop? It's downloaded 80,000 times a week and it's got 2.2 million active installations on a weekly basis. What about those folks? So we decided to raise the bar again and say, "Hey, let's make sure that this partnership includes "not only Docker Hub but Docker Desktop, so you'll be able, when we launch this, to scan your images locally on Docker Desktop. >> Awesome, I see getting some phone calls and then you got to hit this, hit the end button real quick. I saw that in there. I've got an interesting chat I want to just kind of lighten things up a little bit from Brian Stevenson. He says, "Justin, what glasses are those?" (Justin laughing) So he wants to know what kind of glasses you're wearing. >> They're glasses that I think signal that I turned 40 last year. >> (laughs) I'd say it's for your gaming environments, the blue light glasses. >> But I'm not going to say where they came from because it's probably not going to engender a bunch of positive good. But they're nice glasses. They help me see the computer screen and make sure that I'm not a bad fingering my CLI commands >> Well as old guys need the glasses, certainly I do. Speaking of old and young, this brought up a conversation since that came up, I'll just quickly riff into this cause I think it's interesting, Kelsey Hightower, during the innovation panel talked about how the developers and people want to just do applications, someone to get under the hood, up and down the stack. I was riffing with John Chrysler, around kind of the new generation, the kids coming in, the young guns, they all this goodness at their disposal. They didn't have to load Linux on a desktop and Rack and Stack servers all that good stuff. So it's so much more capable today. And so this speaks to the modern era and the expansion overall of opensource and the expansion of the people involved, new expectations and new experiences are required. So as a product person, how do you think about that? Because you don't want to just build for the old, you got to build for the new as well as the experience changes and expectations are different. What's your thoughts around that? >> Yeah, I think about sort of my start in this industry as a really good answer to that. I mean, I remember as a kid, I think I asked for a computer for every birthday and Christmas from when I was six, until I got one given to me by a friend's parents in 1994, on my way off to boarding school. And so it took that long just for me to get a computer into my hands. And then when I was in school there wasn't any role sort of Computer Science or coding courses until my senior year. And then I had to go to an Engineering School at Rensselaer city to sort of get that experience at the time. I mean, just to even get into this industry and learn how to code was just, I mean, so many things had to go my way. And then Microsoft hired me out of college. Another thing that sort of fell my way. So this work that we're doing is just so important because I worked hard, but I had a lot of luck. But not everybody's going to have some of that, right? Have that luck. So how can we make it just as easy as possible for folks to get started wherever you are. If you have a family and you're working another full time job, can you spend a few hours at night learning Docker? We can help you with that. Download Docker Desktop. We have tutorials, we have great docs, we have great captains who teach courses. So everything we're doing is sort of in service of that vision and that democratization of getting into the ideas. And I love what Kelsey, said in terms of, let's stop talking about the tech and let's stop talking about what folks can do with the tech. And that's very, very poignant. So we're really working on like, we'll take care of all the complexity behind the scenes and all of the VMs and the launching of containers and the network. We'll try to help take care of all that complexity behind the curtain so that you can just focus on getting your idea built as a developer. >> Yeah, and you mentioned Kelsey, again. He got a great story about his daughter and Serverless and I was joking on Twitter that his daughter convinced them that Serverless is great. Of course we know that Kelsey already loves Serverless. But he's pointing out this developer dopamine. He didn't say that's Shawn's word, but that's really what his daughter wanted to do is show her friends a website that she built, not get into, "Hey look, I just did a Kubernetes cluster." I mean it's not like... But pick your swim lane. This is what it's all about now. >> Yeah, I hope my son never has to understand what a service mesh is or proxy is. Right? >> Yeah. >> I just hope he just learn the language and just learns how to bring an idea to life and all the rest of it is just behind me here. >> When he said I had a parenting moment, I thought he's going to say something like that. Like, "Oh my kid did it." No, I had to describe whether it's a low level data structure or (laughs) just use Serverless. Shifting gears on the product roadmap for Docker, can you share how folks can learn about it and can you give some commentary on what you're thinking right now? I know you guys put on GitHub. Is there a link available-- >> Absolutely, available. Github.com/docker/roadmap. We tried to be very, very poignant about how we named that. So it was as easy as possible. We launched it a few months ago. It was a first in terms of Docker publicly sharing it's roadmap and what we're thinking and what we're working on. And you'll find very clear instructions of how to post issues and get started. What our code of conduct is. And then you can just get started and we even have a template for you to get started and submit an issue and talk to us about it. And internally my team and to many of our engineers as well, we triaged what we see changing and coming into the public roadmap two to three times a week. So for a half an hour to 45 minutes at a time. And then we're on Slack, batting around ideas that are coming in and saying how we can improve those. So for everyone out there, we really do pay attention to this very frequently. And we iterate on it and the image vulnerability scannings one of those great examples you can see some other things that we're working on up there. So I will say this though, there has been some continual asks for our Lennox version of Docker Desktop. So I will commit that, if we get 500 up votes, that we will triage and figure out how to get that done over a period of time. >> You heard 500 up votes to triage-- >> 500 >> You as get that. And is there a shipping date on that if they get the 500 up votes? >> No, no, (John laughs) you went to a shipping date yet, but it's on the public roadmap. So you'll know when we're working on it and when we're getting there. >> I want before I get into your session you had with the capital, which is a very geeky session getting under the hood, I'm more on the business side. The tail wind obviously for Docker is the micro services trend. What containers has enabled is just going to continue to get more awesome and complex but also a lot of value and agility and all the things you guys are talking about. So that obviously is going to be a tailwind for you. But as you guys look at that piece of it, specifically the business value, how is Docker positioned? Because a of the use cases are, no one really starts out microservices from a clean sheet of paper that we heard some talks here DockerCon where the financial services company said, "Hey, it's simple stack," and then it became feature creep, which became a monolith. And then they had to move that technical debt into a much more polyglot system where you have multiple tools and there's a lot of things going on, that seems to be the trend that also speaks to the legacy environment that most enterprises have. Could you share your view on how Docker fits into those worlds? Because you're either coming from a simple stack that more often and got successful and you're going to go microservice or you have legacy, then you want to decouple and make it highly cohesive. So your thoughts. >> So the simple answer is, Docker can help on both ends. So I think as these new technologies sort of gain momentum and get talked about a bunch and sort of get rapid adoption and rapid hype, then they're almost conceived to be this wall that builds up where people start to think, "Well, maybe my thing isn't modern enough," or, "Maybe my team's not modern enough," or, "Maybe I'm not moderate enough to use this." So there's too much of a hurdle to get over. And that we don't see that at all. There's always a way to get started. Even thinking about the other thing, and I'd say, one we can help, let us know, ping us, we'll be happy to chat with you, but start small, right? If you're in a large enterprise and you have a long legacy stack and a bunch of legacy apps, think about the smallest thing that you can start with, then you can begin to break off of that. And as a proof of concept even by just downloading Docker Desktop and visual studio code and just getting started with breaking off a small piece, and improve the model. And I think that's where Docker can be really helpful introducing you to this paradigm and pattern shift of containers and containerized packaging and microservices and production run time. >> And certainly any company coming out of his post pandemic is going to need to have a growth strategy that's going to be based on apps that's going to be based on the projects that they're currently working, double down on those and kind of sunset the ones that aren't or fix the legacy seems to be a major Taylor. >> The second bit is, as a company, you're going to also have to start something new or many new things to innovate for your customers and keep up with the times and the latest technology. So start to think about how you can ensure that the new things that you're doing are starting off in a containerized way using Docker to help you get there. If the legacy pieces may not be able to move as quickly or there's more required there, just think about the new things you're going to do and start new in that respect. >> Well, let's bring some customer scenarios to the table. Pretend I'm a customer, we're talking, "Hey Justin, you're looking good. "Hey, I love Docker. I love the polyglot, blah, blah, blah." Hey, you know what? And I want to get your response to this. And I say, "DevOps won't work here where we are, "it's just not a good fit." What do you say when you hear things like that? >> See my previous comment about the wall that builds up. So the answer is, and I remember hearing this by the way, about Agile years ago, when Agile development and Agile processes began to come in and take hold and take over for sort of waterfall processes, right? What I hear customers really saying is, "Man, this is really hard, this is super hard. "I don't know where to start, it's very hard. "How can you help? "Help me figure out where to start." And that is one of the things that we're very very very clearly working on. So first off we just, our docs team who do great work, just made an unbelievable update to the Docker documentation homepage, docs.docker.com. Before you were sort of met with a wall of text in a long left navigation that if you didn't know what you were doing, I would know where to go. Now you can go there and there's six very clear paths for you to follow. Do you want to get started? Are you looking for a product manual, et cetera. So if you're just looking for where to get started, just click on that. That'll give you a great start. when you download Docker Desktop, there's now an onboarding tutorial that will walk you through getting your first application started. So there are ways for you to help and get started. And then we have a great group of Docker captains Bret Fisher, many others who are also instructors, we can absolutely put you in touch with them or some online coursework that they deliver as well. So there's many resources available to you. Let us help you just get over the hump of getting started. >> And Jenny, and on the community side and Peter McKee, we're talking about some libraries are coming out, some educational stuff's coming around the corner as well. So we'll keep an eye out for that. Question for you, a personal question, can you share a proud devOps Docker moment that you could share with the audience? >> Oh wow, so many to go through. So I think a few things come to mind over the past few weeks. So for everyone that has no... we launched some exciting new pricing plans last week for Docker. So you can now get quite a bit of value for $7 a month in our pro plan. But the amount of work that the team had to do to get there was just an incredible thing. And just watching how the team have a team operated and how the team got there and just how they were turning on a dime with decisions that were being made. And I'm seeing the same thing through some of our teams that are building the image vulnerability scanning feature. I won't quote the number, but there's a very small number of people working on that feature that are creating an incredible thing for customers. So it's just how we think every day. Because we're actually almost trying to productize how we work, right? And bring that to the customer. >> Awesome, and your take on DockerCon virtual, obviously, we're all in this situation. The content's been rich on the site. You would just on the captains program earlier in the day. >> Yes. >> Doctor kept Brett's captain taught like a marathon session. Did they grill you hard or what was your experience on the captain's feed? >> I love the captain's feed. We did a run of that for the Docker birthday a few months ago with my co-worker Justin Cormack. So yes, there are two Justin's that work at Docker. I got the internal Justin Slack handle. He got the external, the community Slack Justin handle. So we split the goods there. But lots of questions about how to get started. I mean, I think there was one really good question there. Someone was saying asking for advice on just how to get started as someone who wants to be a new engineer or get into coding. And I think we're seeing a lot of this. I even have a good friend whose wife was a very successful and still is a very successful person in the marketing field. And is learning how to code and wants to do a career switch. Right? >> Yeah. >> So it's really exciting. >> DockerCon is virtual. We heard Kelsey Hightower, we heard James Governor, talk about events going to be more about group conventions getting together, whether they're small, medium, or large. What's your take on DockerCon virtual, or in general, what makes a great conference these days? Cause we'll soon get back to the physical space. But I think the genie's out of the bottle, that digital space has no boundaries. It's limitless and creativity. We're just scratching the surface. What makes a great event in your mind? >> I think so, I go back to thinking, I've probably flown 600,000 miles in the past three years. Lots of time away from my family, lots of time away from my son. And now that we're all in this situation together in terms of being sheltered in place in the global pandemic and we're executing an event that has 10 times more participation from attendees than we had in our in person event. And I sat back in my chair this morning and I was thinking, "Did I really need to fly that 600,000 miles "in the past three years?" And I think James Governor, brought it up earlier. I really think the world has changed underneath us. It's just going to be really hard to... This will all be over eventually. Hopefully we'll get to a vaccine really soon. And then folks will start to feel like world's a little bit more back to "normal" but man, I'm going to really have to ask myself like, "Do I really need to get on this airplane "and fly wherever it is? "Why can't I just do it from my home office "and give my son breakfast and take them to school, "and then see them in the evening?" Plus second, like I mentioned before in terms of access, no in person event will be able to compete ever with the type of access that this type of a platform provides. There just aren't like fairly or unfairly, lots of people just cannot travel to certain places. For lots of different reasons, monetary probably being primary. And it's not their job to figure out how to get to the thing. It's our job to figure out how to get the tech and the access and the learning to them. Right? >> Yeah (murmurs) >> So I'm super committed to that and I'll be asking the question continually. I think my internal colleagues are probably laughing now because I've been beating the drum of like, "Why do we ever have to do anything in person anymore?" Like, "Let's expand the access." >> Yeah, expand the access. And what's great too is the CEO was in multiple chat streams. So you could literally, it's almost beam in there like Star Trek. And just you can be more places that doesn't require that spatial limitations. >> Yeah. >> I think face to face will be good intimate more a party-like environment, more bonding or where social face to face is more impactful. >> We do have to figure out how to have the attendee party virtually. So, we have to figure out how to get some great electronic, or band, or something to play a virtual show, and like what the ship everybody a beverage, I don't now. >> We'll co-create with Dopper theCUBE pub and have beer for everybody if need they at some point (laughs). Justin, great insight. Thank you for coming on and sharing the roadmap update on the product and your insights into the tech as well as events. Appreciate it, thank you. >> Absolutely, thank you so much. And thanks everyone for attending. >> Congratulations, on all the work on the products Docker going to the next level. Microservices is a tailwind, but it's about productivity, simplicity. Justin, the product, head of the product for Docker, VP of product on here theCUBE, DockerCon 2020. I'm John Furrier. Stay with us for more continuous coverage on theCUBE track we're on now, we're streaming live. These sessions are immediately on demand. Check out the calendar. There's 43 sessions submitted by the community. Jump in there, there are own container of content. Get in there, pun intended, and chat, and meet people, and learn. Thanks for watching. Stay with us for more after this break. (upbeat music)

>>From around the globe. It's the queue with digital coverage of Docker con live 2020 brought to you by Docker and its ecosystem partners. >>Okay, everyone. Welcome back. We're in between segments, we just had Sydney from engine on Jenny, Peter. We're getting down to the last stretch. So our last little segment, before we go to the full wrap up where Jenny, you're going to give away the awards, Peter going to give it away. The awards for the captains, the community. How are you guys feeling? >>Right? Um, I'm feeling great. Peter, how about you? >>Awesome. It's been, it's been fun. Well, Peter, your internet celebrity. Now I hear, I don't know. Is there a special tweet we want to show? I think so. Okay. You see that tweet? It says you're internet famous. Your mom and dad are watching your presentation. Jenny, can you read that? Yeah. >>Yeah. And to be fair, right? They didn't tweet it. They, uh, they watched either session and, and joined and typed in the comments, even though, uh, they had to ask if he was speaking English. Cause they didn't understand anything. He was saying. >>I saw in the chat, I saw my dad's name go by and just, >>I feed her, but wait a minute. And then my wife >>Came in later, said, yeah, your mom and dad are watching your talk. Do we, do we ever stop parenting? >>I don't. Well, I had the opposite effect. I was in one of the sessions and I see a great comment. I'm like, who wrote this? It's my son, Alec farrier, like son, get out of the chat. He said, it's a dope. He said, it's a dope session. It could have been worse. Went in totally random. So it was good. Just look at it, which everywhere the cube and dr. Khan, what a great, uh, no boundaries, age geography has been. I'm really blown away guys. I really gotta say I'm super impressed with the community content program you put together. It's been so much fun. I learned so much. And so appreciate it. Thank you. >>Oh, thank you. I have to agree. Uh, Amanda silver said earlier that coding is the, and you know, Docker con is a team sport too. Uh, I have to take some time to think all the people, uh, that have participated in helped make this event so great. And we'll definitely do it again as we give out the community awards at the end. Okay. I guess 40 minutes from now, but thank you to the doctor theme. Um, many of them have been awakened for hours and hours, hours helping engage and have a great time. Thank you. Okay. Okay. An awesome platform. Rocks scheduling is next level. Um, and the captains, right? I don't know if anyone's had the chance that's watching to go check out the captain stream, especially Brett Fisher. Who's been on all day and he's been so involved in helping us plan to make sure that this is a conversation and not a large webinar. Right. Um, and then our sponsors, we could not have done this without our sponsors. They've been delivering great talks. They're all on demand, uh, except for the one coming up. So make sure to catch those. They'll have giveaways as well, um, that you can, that you can join into two more speakers. You've done awesome, uh, content and production. And then of course the thoughtfulness of the community, right. Thank you for bringing it here today, around the world. >>That's awesome. And I always just say the content presentations were really, really good. The graphics there's templates, but the work that was put into the video and the demos really just next level, as you said. So really just great. I mean, that makes the conference is the presentation. So those talks were engaging. Um, the comments were awesome. Again, I learned a ton and I love love when it's dynamic like that. Uh, Peter, you gotta be psyched developer relations, any, any new insights on the, uh, from the devs? >>Oh, it was great. Great talks. A lot of great. And I was really, really surprised with the chat that the interaction was tremendous. Uh, and I can't believe I used tremendous, but we'll just skip that anyways. Um, but also check out, uh, hashtag Docker con jobs. If you're looking for a job or if you have openings, please, please, uh, hashtag that in your, in your tweets, um, want to help the community out as much as possible. There's a ton of work out there. Just gotta help connect everybody and love to be part of that for sure. >>Yeah. Just so you know, in case you missed the Justin Warren who was live said on live cube, Docker TV, that if he gets 500 upvotes on Linux for Docker, desktop, I think it was. Or was it hub? Might've been desktop. I think he'll triage it out. So there it is. >>All right. I hope the internet heard that cause that's a popular one for sure. Yeah. >>He was on the record and he leaned in on that too. He said it like that. So he meant cool. Any other, uh, shout outs? I mean, I thought Brad was great. Um, the, his, uh, posse, uh, captains were amazing. Um, good feedback there. So gruesome some great chit chatter on that. Um, I didn't have a chance to peek into the session because we're hosting these mainstreams, but yeah. What are you hearing on the captains? >>Uh, tons of knowledge being dropped on that channel for sure. And really great in depth conversations there, uh, answering questions, interacting with the audience. Uh, and you know, a lot of these captains are teachers, uh, as their, as their day job. And a lot of them have, uh, fabulous Docker and Kubernetes content and are running sales right now. So if you do want learn more, if you like, what you heard today, definitely check out right? The horses are on sale this week or under $10, a huge investment in your future. And then Manning books is also running a promotion, a DTW Docker 20 for 40% off their content and a dr. Popkin Elton Stoneman, Jeff Nicola they'll have content there as well. And then Nigel, uh, is, is, has a number of training, uh, courses and, and books as well to check out. Um, and then the captains are running a charity stream. Awesome. People have been donating all day. It's been awesome. Uh, Docker's going to make sure that we reach our $10,000 goal. They wanted to announce that as well. >>I noticed cockroach labs had a similar thing for women for coding. They had another kind of virtual bag swipe. So check them out. They're donating cash as well to women who code. Okay. >>Right. >>Which is very cool. Um, anything else that we missed? Swag giveaways? >>I have one little, um, little comment, a little secret. So I don't know if anybody's caught it yet, Jenny, but if you go back and watch the, the, uh, you know, with Scott, there might be a surprise in there and anybody that finds it first and tweets me might have something for you. >>So Easter egg in there. Is there something going on there? >>I went on, I don't know. I'm just, just saying, >>Okay. All right. Check out the keynote. That was a pro tip right there for everyone's watching. So if you're watching this stream right now, as we get into our awesome next segment, which is going to be really one of my favorites, the children's cancer Institute, this was not only a moving segment from an impact standpoint, but talking about the people that interns and young developers really solving a big problem with Docker, this is a really high impact statement. So that segment, so, so watch it guys. Thanks so much. We'll see. On the wrap up after this next segment, of course, does the catalog of content in the schedule when it's not streaming, it becomes a catalog. So if you're watching it, check out all the sessions, we'll see you in the wrap up.

>> Announcer: From around the globe, it's theCUBE with digital coverage of DockerCon Live 2020. Brought to you by Docker and its ecosystem partners. >> Okay Jenny, great to see you again. >> Good to see you. >> James Governor, nail on the Keynote there. Chat was phenomenal. That was pre-recorded but James is also in the chat stream. A lot of good conversations. That hit home for me that keynote. One, because memory lane was going down right into the 80s when it was a revolution. And we got him in the green room here. James Governor, welcome. >> James is here, hi James. >> Here we go. >> Fresh off the keynote. >> It's always a revolution. (John laughs) >> Well, in the 80s, I used to love your talk. A couple of key points I want to share and get your thoughts on was just to some highlights for the crowd is one, you walk through. Some of the key inflection points that I think were instrumental and probably some other ones depending on your perspective of where you were in the industry at that time. Whether you were a systems programmer or a networking guy, there was a proprietary world and it was a revolution back then. And UNIX was owned by AT&T if no one remembers. You couldn't even use the word. You had to trade market. So we actually had to call it XINU which is UNIX spelled backwards in all the text and whatnot. And even open source software freeware was kind of illegal. MIT did some work, Northeastern and Berkeley and other schools. It was radical back then so-- >> Yeah, we've come a long way for sure. I think that for me that was one of the things that I wanted to really point to in the keynote was that yes we have definitely come a long way and development culture is about open culture. >> I think the thing that I like to point out especially hate to sound like I'm old but I am. But I lived through that and the younger generation coming and have all these new tools. And I got to say not that I walked through to school in the snow with no shoes on but it's a pretty cool developer environment now. But remember things were proprietary back then. If you start to see the tea leaves now, I look at the world, you see these silos. You see silos that's kind of, they're not nestle proprietary but they might necessarily be open. So you kind of have a glimpse of open source on these projects and these companies. Whether they're tech companies, it feels open but it might not be. It could be walled garden. It could be data being hoarded. So as data opens up, this is interesting to me because I want to get your thoughts on this because in a way it feels proprietary but technically it's not proprietary. What's your thoughts on this? Because this is going to be the next 20 years of evolution. What's your thoughts? >> I think the productivity wins. Whoever packages technology in a way that makes it most productive for people. That's what wins. And open source, what's productive. It is very accessible. It enabled new waves. Get installed and you've got a package from... You got access to just a world of open-source. A world of software that was a big revolution. And I guess the cloud sort of came next and I think that's been one of the big shifts. You talk about proprietary. What matters is how easy you make things to people to do their work. And in that regard, obviously Amazon is in fact a bigger distribution network. Makes technology super consumable by so many people. I guess I would say that open is good and important but it's not the only thing. As you say, data is a lock-in and it's right and people are choosing services that make them productive. Nobody worries about whether Amazon Lambda is proprietary. They just know that they can build companies or businesses or business processes on it. >> You know it's interesting back in the day just to kind of segue with the next topic. We were fighting proprietary operating systems, UNIX and others. We're also fighting for proprietary Network protocol stacks. SNA was owned by IBM. DECnet was digital, the number one network. And then TCP/IP and OpenSan's interconnect came out. That's the OSI model for us old ones. That set the table. That changed the face of everything. It really enabled a lot. So when I see containers, what Docker did early on the pioneering phases of Docker containers, it unleashed a new reality of coolness and scale and capabilities. And then in comes Kubernetes and in comes micro services. So this path is showing some real strength for new kinds of capabilities. So how does a developer navigate all this because data lock-in does it a data plane seems to be a control point. What are we fighting now in your opinion? shouldn't say we're fighting but what are we trying to avoid if operating systems was for closing opportunities and network protocol stacks before closing in the past? What do you see as barriers that need to be broken down in the open source world around going down this great path of micro services, decomposed applications, highly cohesive architectures? >> Honestly there's enough work to be getting on with without like fighting someone in that regard. I mean we're fighting against technical debt. I just don't think that people are serrated about fighting against proprietary anymore. I think that's less than a concern. Open-source technology is great. It's how most work gets done in our industry today. So you mentioned Kubernetes and certainly Docker. Though we did a phenomenal job of packaging up and experience that map to see CICD. That map to the developer workplace people like do. Phenomenal job and I think that for me at least when I look at where we are as an industry, it's all about productivity. So there are plenty of interesting new platforms. I think in my keynote, that's my question. I'm less interested in microservices than I am in distributed work. I'm interested in one of the tools that are going to enable us to become more productive, solve more problems, build more applications and get better at building software. So I think that's my sort of focus. There will always be lock-in. And I think you will also have technologies mitigate against that. I mean clear messages today from Docker about supporting multiple clouds. For a while at least multiclouds seem like something only the kind waivers were interested in but increasingly we're seeing organizations where that is definitely part of how they're using the cloud. And again I think very often it's within specific areas. And so we see organizations that are using particular clouds for different things. And we'll see more of that. >> And the productivity. I love the passion, love that in the keynote. That was loud and clear. Two key points I want to get your reaction on that. You mentioned one was inclusion. Including more people, not seeing news. It's kind of imperative. And also virtual work environments, virtual events. You kind of made a highlight there. So again people are distributed remote first. It's an opportunity to be productive. Can you share your thoughts on those two points? One is, as we're distributed, that's going to open the aperture of more engagement. More people coming in. So code of conduct not as a file you must read or some rule. Culturally embracing a code of conduct. And then also, virtual events, virtual groups convening like we're doing here. >> Yeah I mean for me at least Allison McMillan from github and she just gave such a great demo at the recent sunlight event where she finished and she was like, it was all about, I want to be able to put the kids to bed for a nap and then go code. And I think that's sort of thinking people band around the phrase ruling this together but I mean certainly parenting is a team sport. But I think it's interesting we're not welcome. It was interesting that was looking at the chat, going through, I was being accused of being woke. I was being accused of being a social justice warrior. But look at the math. The graph is pretty clear. Women are not welcomed in tech. And that means we're wasting 50% of available resource to us. And we're treating people like shit. So I thought I underplayed that in the talk actually. Something like, "Oh, why is he complaining about Linus?" Well, the fact is that Linus himself admitted he needed to change his persona in order to just be more modern and welcoming in terms of building software and building communities. So look we've got people from around the world. Different cultural norms. All of the women I know who work in tech suffer so much from effectively daily harassment. Their bonafides are challenged. These are things that we need to change because women are brilliant. I'm not letting you signaling or maybe I am. The fact is that women are amazing at software and we do a terrible job of supporting them. So women of other nationalities, we're not going to be traveling as much. I think you can also grow. No we can't keep flying around as much. Make an industry where single parents can participate more effectively. Where we could take advantage of that. There're 200 million people in Nigeria. That hunger to engage. We won't even give them a visa and then we may not be treating them right. I just think we need an industry reset. I think from a we need to travel less. We need to do better work. And we need to be more welcoming in order that that could be the case. >> Yeah, there's no doubt a reset is here and you look at the COVID crisis is forcing that function there because one, people are resetting and reinventing and trying to figure out a growth strategy. Whether it's a business or teams. And what's interesting is new roles and new responsibilities is going to emerge and I think you're right about the women in tech. I completely agree and have evidence myself and reported on it ad nauseam. But the thing is data trumps opinion. And the data is clear on this issue. So if anyone will call you a social justice warrior I just say pound sand and tell them that go on their way. And just look at the data and clear. And also the field is getting wider. When I was in computer science major back in the day, it was male-dominated yes but it was very narrow. Wasn't as broad as it is now. You can do things so much more and in fact in Kelsey Hightower's talk, he talks to persona developers. The ones that love to learn and ones that don't want to learn anything. Just want to code and do their thing. And ones that care about just app development and ones that just want to get in and sling k-8 around like it's nobody's business or work with APIs, work with infrastructure. Some just want to write code. So there's more and more surface area in computer science and coding. Or not even computer science, it's just coding, developing. >> Well, I mean it's a bigger industry. We've got clearly all sorts of challenges that need to be solved. And the services that we've got available are incredible. I mean if you look at the work of companies like Netlify in terms of developer experience. You look at the emergence of JamStack and the productivity that we're seeing there, it's a really exciting time in the industry. >> No doubt about that. >> And as I say I mean it's an exciting time. It's a scary time. But I think that we're moving to a world of more distributed work. And that's my point about open source and working on code bases from different places and what the CapCloud can enable. We can work in a different way and we don't all need to be in San Francisco, London, or Berlin as I said in the Keynote. >> I love the vision there and the passion. I totally agree with it. I think that's a whole another distributed paradigm that's going to move up the stack if you will and software. I think it's going to be codified in cloud native and cloud scale creates new services. I mean it's the virtual world. You mentioned virtual events. Groups convening like the 67,000 people coming together virtually here at DockerCon. Large, small one-on-ones group dynamics are a piece of it. So share your thoughts on virtual events and certainly it's people are now just kicking the tires, learning. You do a zoom, you do a livestream. You do some chat. It's going to evolve and I think it's going to look more like a CICD pipeline and anything else. As you start to bring media together, we get 43 sessions here. Why not make it a hundred sessions? So I think this is going to be one of those learning environments where it's not linear, it's different. What's your vision of all this if you had to give advice for the folks out there? Not event plans, with people who want to gather groups and be productive. What's your thinking on this? >> Well, it sort of has to happen. I mean there are a lot of people doing good work in this regard. Patrick Dubois, founder of DevOps days. He's doing some brilliant work delineating. Just what are all the different platforms? What does the streaming platform look like that you can use? Obviously you've got one here with theCUBE. Yeah, I mean I think the numbers are pretty clear. I mean Microsoft Build had 245,000 registered attendees and I think something that might have been to begin. The patterns are slightly different. It's not like they're going to be there the whole time but the opportunity to meet people where they are, I think is something that we shouldn't ignore. Particularly in a world not everyone again has the privilege of being able to travel. You're in a different country or as I say perhaps your life circumstances mean you can't travel. From an accessibility perspective, clearly virtual events offer an opportunity that we haven't fully nailed. I think Microsoft performance in this regard has been super interesting. They were already moving that way and Kobe just slammed it up to another level. What they did with Build recently was actually, I mean they're a media company, right? But certainly developed a focused media company. So I think you'll be okay. You're about the business of software John. Don't worry Microsoft don't give you some space there. (John and James laughing) We're under the radar at theCUBE 365 for the folks who are watching this. This is our site that we built with our software. So we're open and Docker was instrumental and I think the Docker captains were also very instrumental and trying to help us figure out the best way to preserve the content value. I personally think we're in this early stage of, content and community are clearly go hand in hand and I think as you look at the chat, some of the names that are on there. Some of the comments, really there's a new flywheel of production and this to me is the ultimate collaboration when you have these distinct groups coming together. And I think it's going to just be a data dream where people aren't the product, they're actually a contributor. And I think this open source framework that you're talking about is going to be certainly just going to evolve rapidly. I think it's just not even scratching the surface. I just think this is going to be pretty massive. And services whatever you want to define that. It could be an API to anything. It's going to be essentially the scale point. I mean why have a monolith piece of software running something. Something Microsoft teams will work well here. Zoom will work well there but ultimately what's in it for me the person? This is the key question. Developers just want to develop. You're going to hear that throughout the day. Kelsey Hightower brings up some great points in his session and Amanda silver at Microsoft, she had a quote on one of her videos. She said, "App developers are the first responders "in this crisis." And that's the first time I've heard someone say that out loud and that hits home for me because it's true. And right now app developers are one of the front lines. They're providing the app support. They're providing to the practitioners in the field. This is something that's not really written about in the press. What's your reaction to app developers are the first responders in this crisis. >> Well I mean first I think it's important to pay tribute to people that actually are first responders. Writing code can make us responsive but let's not forget there are people that are lacking PPE and they are on the frontline. So not precise manner but I might frame it slightly differently. But certainly what the current situation has shown us is productivity is super important. Target has made huge investments in building out its own software development capabilities. So they used to be like 70% external 30% internal and they turn that round to like 80% internal 20 external. And they've been turning on a dime and well there's so much going on at the moment. I'm like talking about target then I'm remembering what's happening in Minneapolis today. But anyway we'll talk about that. But yeah organizations are responding quickly. Look at the numbers that Shopify is happening because all sorts of business is something like we need to be an online business. What's the quickest way to do that. And Shopify was able to package something up in a way that they they could respond to challenges. Huge social challenges. I'm a big believer the future's unwritten at this point and I think there's a lot of problems out there you point out and the first responders are there I agree. I'm just thinking that there's got to be a better path for all of us. And this brings up the whole new roles and responsibilities around this new environment and I know you're doing a lot of research. Can you share some thoughts on what you're kind of working on now James? That's important, I'll see what's trending here at DockerCon is. Compose the relationship with Microsoft, we've got security, Dockers now, multicloud approach, making it easier, that's their bread and butter. That's what they're known for. They kind of going back to that roots of why they pioneered in the first place. So as that continues ease-of-use, what's your focus area right now that you're researching that you could share with the audience? >> Well, I mean I'd say this year for me I've got probably three key areas. One is what's called GitOps. So it's the notion that you're using Git as a system of record. So that started off randomly making changes, you have an audit trail. You begin to have some sort of sense of compliance in software changes. I think the idea of everything has to be by a sort of a pull request. That automation model is super thing to me. So I've been looking at that. A lot of development teams are using those approaches. Observability is a huge trend. We're moving to the idea of testing and production. The kind of stuff that's been evangelized so successfully by charity majors honeycomb. It's super exciting to me and it's true because in effect, you're always testing in production, your dev environment. I mean we used to have this idea that you'd have a Dev and a Dev stage. You're have a staging environment. The only environment that really matters is where the rubber meets the road. And that is deployment. So I think that having having better tools for that is one of the areas I'm looking at. So how are tools innovating that area? And it won't be the thing that this is my own personal thing. I've been talking about progressive delivery which is asking a question about reducing risk by really understanding the blast radius of the service to be able to roll it out to specific use of populations first. Understanding who they are and enrolling it up so it's the idea that like maybe you brought something out to your employees first. Maybe you are in California and you roll something out in Tokyo knowing that not many people are using that service. It is a live environment but people are not going to be adversely affected if it happens. So Canary's Blue-Green deployments and also experimentation. This is sort of one of the areas I'm being sort of pulled towards. It's sort of product management and how that's really converging with software development. I feel like that's one of the things I haven't fully, I mean I think it's when they have research focused but you have to respond to new information. Anyhow, I'm spending a lot of time thinking about the world of product management. It's those companies to be most respect in terms of companies that are crushing it in the digital economy. They have such a strong product management focused. Everything is driven by product managers that understand technology and that's an exciting shift. The one that I'm paying greater attention. >> You do some great work and I love the focus on productivity software development. Getting those app developers out there and it's interesting. I just think that it's such an exciting time. It's almost intoxicating. Some people drinking on Twitter online and having beers because they're in different time zone. But if you look up and down the action that's going on, you got at the application developers side, all the things you were mentioning services. But when you look at the cloud side, you got almost this operating system reset. It's a systems architecture. So you have the hall and that's up and down. The middle of the stack to the bottom, you have this operating systems thinking and evolution. And then you got at the top, the pure software developers. And this is again to me the big aha moment. For the industry there's a true opportunity to scale that in unbelievable ways. And you don't have to pick a side. You can do a top of the stack bottom stack. So I think kubernetes and micro services really bring this whole enablement piece to the table. And that fascinates me and I think that's going to change what the apps will look like. It'll give more productivity and then making the internet programmable unit, that's new systems. So that seems to be the trend. You're a systems guy, your girl or you're a developer. How do you see that evolving? Do you get to that level? >> Developer experience is not necessarily the key value of Kubernetes. It's supremely flexible sort of system. It does offer you that portability. But I think what I'm seeing now is how people are taking Kubernetes and kind of thinking, so you've got VMware, acquires Heptio, brings Pivotal into the fold, starting about what that platform looks like. I think Pivotal with cloud foundry did a great job of thinking through operator experience. Operator experience is not the same as developer experience. I think we're going to see a bit more specialization of roles. Meanwhile at that point, you've got the cloud players all doing pretty awesome job supporting Kubernetes. But it gives that portability promise. So I think for me, one of the things is not expecting everyone to do everything. It's like Kelsey said, some people just want to come into work and do their job and they're super important. And so VMware I think a history of certification of application environments. So of them it's sort of quite--and certification of humans. It's quite natural that they would be somebody that would think about how do we make Kurbenetes more consumable and packaged in a way that more people take advantage of it. Docker was such a phenomenon and now seeing how that sort of evolving into that promise of portability is beginning to be realized. So I think the specialization, the pendulum is going to swing back just a little bit. >> I think it's just great timing and congratulations on all the work and thanks for taking the time for participating in DockerCon with the Keynote. Taking time out of your day and coming in and doing this live interview. The chat looks good. Hit some great, get some fans in there. It's a great opportunity and I think Docker as the pioneers, pivoting in a new direction, it's all about developer productivity and James you've been on it. @monkchips is his Twitter handle, follow him, hit him up. I'm John Furrier here in the studio for DockerCon 2020. Ginebra CEO and you got Brett Fisher on the captain's channel. If you go to the site, you'll see the calendar. Jump into any session you want. They'll be live on the time or on-demand instantly. TheCUBE track has a series of enemies. You've got Amazon, we got Microsoft, get some great guests, great practitioners that are literally having an impact on society. So thanks for watching. James, thanks for spending the time. >> Thank you very much John. >> Okay James Governor, founder of Monkchips, great firm, great person-- >> RedMonk, RedMonk is the company. Monkchips is the Twitter. >> Redmonk, Monkchips. RedMonk, RedMonk. >> RedMonk is the company. >> RedMonk, RedMonk. >> @monkchips is his Twitter handle and RedMonk is the firm, thank you for the correction. Okay more coverage DockerCon after this short break. Stay with us. The next segment is coming up. Stay with us here at theCUBE DockerCon. (gentle music)

>> From around the globe. It's theCUBE, with digital coverage of DockerCon Live 2020. brought to you by Docker and its ecosystem partners. >> Hello and welcome to DockerCon 2020. I'm John Furrier here in the DockerCon virtual studios. It's CUBE studios it's theCUBE virtual meets DuckerCon 2020 virtual event with my coach, Jenny Barocio and Peter McKee, as well as Brett Fisher, over on the captains who's doing his sessions. This is the wrap up of the long day of continuous amazing action packed DockerCon 2020. Jenny and Peter, what a day we still got the energy. We can go another 24 hours, let's do it now. This is a wrap up. So exciting day, tons of sessions, great feedback. Twitter's on fire the chats and engagements are on fire, but this is the time where we do the most coveted piece, the community awards, so Jenny, this is the time for you to deliver the drum roll for the community awards, take it away. >> Okay, (mumbles) It's the past few years and have been able to recognize those in the community that deliver so much to everyone else. And even though we're wrapping up here, there is still other content going on because we just couldn't stop till five o'clock. Peter what's happening right now? >> Yeah, so over in the Devs in Action channel, we have earning Docker Daemon with rootless mode. That's still going on, should be a great talk. And then in the How To channel, we have transforming open source into live service with Docker. They're still running now, two great talks. >> Awesome, and then the captains are still going. I think they probably started the after party already, although this channel's going to wait till, you know, 30 more minutes for that one. So if you're an after party mode, definitely go check out after we announced the awards, Brett and Marcos and Jeff and the captain's channel. So, we have some great things to share. And I mentioned it in my last segment, but nothing happens without the collective community. DockerCon is no exception. So, I really just want to take a moment again to thank the Docker team, the attendees, our sponsors and our community leaders and captains. They've been all over the virtual conference today, just like they would have been at a real conference. And I love the energy. You know, as an organizer planning a virtual event, there's always the concern of how it's going to work. Right, this is new for lots of people, but I'm in Florida and I'm thrilled with how everyone showed up today. Yeah, for sure. And to the community done some excellent things, Marcus, over them in the Captain's channel, he has built out PWD play with Docker. So, if you haven't checked that out, please go check that out. We going to be doing some really great things with that. Adding some, I think I mentioned earlier in the day, but we're adding a lot of great content into their. A lot more labs, so, please go check that out. And then talking about the community leaders, you know, they bring a lot to the community. They put there their free time in, right? No one paying them. And they do it just out of sheer joy to give back to the community organizing events. I don't know if you ever organized an event Jenny I know you have, but they take a lot of time, right? You have to plan everything, you have to get sponsors, you have to find out place to host. And now with virtual, you have to figure out how you're going to deliver the feel of a meetup in virtually. And we just had our community summit the other day and we heard from the community leaders, what they're doing, they're doing some really cool stuff. Live streaming, Discord, pulling in a lot of tools to be able to kind of recreate that, feel of being together as a community. So super excited and really appreciate all the community leaders for putting in the extra effort one of these times. >> Yeah, for really adapting and continuing in their mission and their passion to share and to teach. So, we want to recognize a few of those awesome community leaders. And I think we get to it right now Peter, are you ready? >> Set, let's go for it, right away. >> All right, so, the first community leaders are from Docker Bangalore and they are rocking it. Sangam Biradar, Ajeet singh Raina and Saiyam Pathak, thank you all so much for your commitment to this community. >> All right, and the next one we have is Docker Panang. Thank you so much to Sujay Pillai, did a great job. >> Got to love that picture and that shirt, right? >> Yeah. >> All right, next up, we'd love to recognize Docker Rio, Camila Martins, Andre Fernande, long time community leaders. >> Yeah, if I ever get a chance that's. I have a bunch of them that I want to go travel and visit but Rio is on top of list I think. >> And then also-- >> Rio maybe That could be part of the award, it's, you get to. >> I can deliver. >> Go there, bring them their awards in person now, as soon as we can do that again. >> That would be awesome, that'd be awesome. Okay, the next one is Docker Guatemala And Marcos Cano, really appreciate it and that is awesome. >> Awesome Marcos has done, has organized and put on so many meetups this last year. Really, really amazing. All right, next one is Docker Budapest and Lajos Papp, Karoly Kass and Bence Lvady, awesome. So, the mentorship and leadership coming out of this community is fantastic and you know, we're so thrilled to write, now is you. >> All right, and then we go to Docker Algeria. Yeah we got some great all over the country it's so cool to see. But Ayoub Benaissa, it's been great look at that great picture in background, thank you so much. >> I think we need we need some clap sound effects here. >> Yeah where's Beth. >> I'm clapping. >> Lets, lets. >> Alright. >> Last one, Docker Chicago, Mark Panthofer. After Chicago, Docker Milwaukee and Docker Madison one meet up is not enough for Mark. So, Mark, thank you so much for spreading your Docker knowledge throughout multiple locations. >> Yeah, and I'll buy half a Docker. Thank you to all of our winners and all of our community leaders. We really, really appreciate it. >> All right, and the next award I have the pleasure of giving is the Docker Captain's Award. And if you're not familiar with captains, Docker captains are recognized by Docker for their outstanding contributions to the community. And this year's winner was selected by his fellow captains for his tireless commitment to that community. On behalf of Docker and the captains. And I'm sure the many many people that you have helped, all 13.3 million of them on Stack Overflow and countless others on other platforms, the 2020 tip of the Captain's Hat award winner is Brandon Mitchell, so so deserving. And luckily Brandon made it super easy for me to put together this slide because he took his free DockerCon selfie wearing his Captains' Hat, so it worked out perfectly. >> Yeah, I have seen Brandon not only on Stack Overflow, but in our community Slack answering questions, just in the general area where everybody. The questions are random. You have everybody from intermediate to beginners and Brandon is always in there answering questions. It's a huge help. >> Yeah, always in there answering questions, sharing code, always providing feedback to the Docker team. Just such a great voice, both in and out for Docker. I mean, we're so proud to have you as a captain, Brandon. And I'm so excited to give you this award. All right, so, that was the most fun, right? We get to do the community awards. Do you want to do any sort of recap on the day? >> What was your favorite session? What was your favorite tweet? Favorite tweet was absolutely Peter screenshotting his parents. >> Mom mom my dear mom, it's sweet though, that's sweet. I appreciate it, can't believe they gave me an award. >> Yeah, I mean, have they ever seen you do a work presentation before? >> No, they've seen me lecture my kids a lot and I can go on about life's lessons and then I'm not sure if it's the same thing but yeah. >> I don't think so. >> No they have never see me. >> Peter you got to get the awards for the kids. That's the secret to success, you know, and captain awards and the community household awards for the kids. >> Yeah, well I am grooming my second daughter, she teaches go to afterschool kids and never thought she would be interested in programming cause when she was younger she wasn't interested in, but yes, super interested in now I have to, going to bring her into the community now, yeah. >> All right, well, great awards. Jenny is there any more awards, we good on the awards? >> Nope, we are good on the awards, but certainly not the thank yous is for today. It's an absolute honor to put on an event like this and have the community show up, have our speakers show up have the Docker team show up, right? And I'm just really thrilled. And I think the feedback has been phenomenal so far. And so I just really want to thank our speakers and our sponsors and know that, you know, while DockerCon may be over, like what we did today here and it never ends. So, thank you, let's continue the conversation. There's still things going on and tons of sessions on demand now, you can catch up, okay. >> One more thing, I have to remind everybody. I mentioned it earlier, but I got to say it again go back, watch the keynote. And I'll say at this time there is an Easter egg in there. I don't think anybody's found it yet. But if you do, tweet me and might be a surprise. >> Well you guys-- >> Are you watching your tweet feed right now? Because you're going to get quite a few. >> Yeah, it's probably blowing up right now. >> Well you got to get on a keynote deck for sure. Guys, it's been great, you guys have been phenomenal. It's been a great partnership, the co-creation this event. And again, what's blows me away is the global reach of the event, the interaction, the engagement and the cost was zero to attend. And that's all possible because of the sponsors. Again, shout out to Amazon web services, Microsoft Azure Engine X, Cockroach Labs and sneak of Platinum sponsors. And also we had some ecosystem sponsors. And if you liked the event, go to the sponsors and say hello and say, thank you. They're all listed on the page, hit their sessions and they really make it possible. So, all this effort on all sides have been great. So, awesome, I learned a lot. Thanks everyone for watching. Peter you want to get a final word and then I'll give Jenny the final, final word. >> No again, yes, thank you, thank you everybody. It's been great, theCUBE has been phenomenal. People behind the scenes has been just utterly professional. And thank you Jenny, if anybody doesn't know, you guys don't know how much Jenny shepherds this whole process through she's our captain internally making sure everything stays on track and gets done. You cannot even imagine what she does. It's incredible, so thank you, Jenny. I really, really appreciate it. >> Jenny, take us home, wrap this up 2020, dockerCon. >> All Right. >> In the books, but it's going to be on demand. It's 365 days a year now, come on final word. >> It's not over, it's not over. Community we will see you tomorrow. We will continue to see you, thank you to everyone. I had a great day, I hope everyone else did too. And happy DockerCon 2020, see you next year. >> Okay, that's a wrap, see on the internet, everyone. I'm John, for Jenny and Peter, thank you so much for your time and attention throughout the day. If you were coming in and out, remember, go see those sessions are on a calendar, but now they're a catalog of content and consume and have a great evening. Thanks for watching. (upbeat music)

>>From around the globe. It's the queue with digital coverage of DockerCon live 2020 brought to you by Docker and its ecosystem partners. >>Hello everyone. Welcome to Docker con 2020 I'm John furrier with the cube. I'm in our Palo Alto studios with our quarantine crew. We have a great lineup here for DockerCon con 2020 virtual event. Normally it was in person face to face. I'll be with you throughout the day from an amazing lineup of content over 50 different sessions, cube tracks, keynotes, and we've got two great co-hosts here with Docker, Jenny Marcio and Brett Fisher. We'll be with you all day, all day today, taking you through the program, helping you navigate the sessions. I'm so excited, Jenny. This is a virtual event. We talk about this. Can you believe it? We're, you know, may the internet gods be with us today and hope everyone's having an easy time getting in. Jenny, Brett, thank you for being here. Hey, >>Yeah. Hi everyone. Uh, so great to see everyone chatting and telling us where they're from. Welcome to the Docker community. We have a great day planned for you >>Guys. Great job. I'm getting this all together. I know how hard it is. These virtual events are hard to pull off. I'm blown away by the community at Docker. The amount of sessions that are coming in the sponsor support has been amazing. Just the overall excitement around the brand and the, and the opportunities given this tough times where we're in. Um, it's super exciting. Again, made the internet gods be with us throughout the day, but there's plenty of content. Uh, Brett's got an amazing all day marathon group of people coming in and chatting. Jenny, this has been an amazing journey and it's a great opportunity. Tell us about the virtual event. Why DockerCon virtual. Obviously everyone's cancelling their events, but this is special to you guys. Talk about Docker con virtual this year. >>Yeah. You know, the Docker community shows up at DockerCon every year and even though we didn't have the opportunity to do an in person event this year, we didn't want to lose the time that we all come together at DockerCon. The conversations, the amazing content and learning opportunities. So we decided back in December to make Docker con a virtual event. And of course when we did that, there was no quarantine. Um, we didn't expect, you know, I certainly didn't expect to be delivering it from my living room, but we were just, I mean we were completely blown away. There's nearly 70,000 people across the globe that have registered for Docker con today. And when you look at backer cons of past right live events, really and more learning are just the tip of the iceberg. And so thrilled to be able to deliver a more inclusive vocal event today. And we have so much planned. Uh, I think Brett, you want to tell us some of the things that you have planned? >>Well, I'm sure I'm going to forget something cause there's a lot going on. But, uh, we've obviously got interviews all day today on this channel with John the crew. Um, Jenny has put together an amazing set of all these speakers all day long in the sessions. And then you have a captain's on deck, which is essentially the YouTube live hangout where we just basically talk shop. Oh, it's all engineers, all day long, captains and special guests. And we're going to be in chat talking to you about answering your questions. Maybe we'll dig into some stuff based on the problems you're having or the questions you have. Maybe there'll be some random demos, but it's basically, uh, not scripted. It's an all day long unscripted event, so I'm sure it's going to be a lot of fun hanging out in there. >>Well guys, I want to just say it's been amazing how you structured this so everyone has a chance to ask questions, whether it's informal laid back in the captain's channel or in the sessions where the speakers will be there with their, with their presentations. But Jenny, I want to get your thoughts because we have a site out there that's structured a certain way for the folks watching. If you're on your desktop, there's a main stage hero. There's then tracks and Brett's running the captain's tracks. You can click on that link and jump into his session all day long. He's got an amazing set of line of sleet, leaning back, having a good time. And then each of the tracks, you can jump into those sessions. It's on a clock. It'll be available on demand. All that content is available if you're on your desktop, if you're on your mobile, it's the same thing. >>Look at the calendar, find the session that you want. If you're interested in it, you could watch it live and chat with the participants in real time or watch it on demand. So there's plenty of content to navigate through. We do have it on a clock and we'll be streaming sessions as they happen. So you're in the moment and that's a great time to chat in real time. But there's more, Jenny, you're getting more out of this event. We, you guys try to bring together the stimulation of community. How does the participants get more out of the the event besides just consuming some of the content all day today? >>Yeah. So first set up your profile, put your picture next to your chat handle and then chat. We have like, uh, John said we have various setups today to help you get the most out of your experience are breakout sessions. The content is prerecorded so you get quality content and the speakers and chat. So you can ask questions the whole time. Um, if you're looking for the hallway track, then definitely check out the captain's on deck channel. Uh, and then we have some great interviews all day on the queue so that up your profile, join the conversation and be kind, right. This is a community event. Code of conduct is linked on every page at the top and just have a great day. >>And Brett, you guys have an amazing lineup on the captain, so you have a great YouTube channel that you have your stream on. So the folks who were familiar with that can get that either on YouTube or on the site. The chat is integrated in, so you're set up, what do you got going on? Give us the highlights. What are you excited about throughout your day? Take us through your program on the captains. That's going to be probably pretty dynamic in the chat too. >>Yeah. Yeah. So, uh, I'm sure we're going to have less, uh, lots of, lots of stuff going on in chat. So no concerns there about, uh, having crickets in the, in the chat. But we're going to, uh, basically starting the day with two of my good Docker captain friends, uh, Nirmal Mehta and Laura taco. And we're going to basically start you out and at the end of this keynote, at the end of this hour, and we're going to get you going. And then you can maybe jump out and go to take some sessions. Maybe there's some cool stuff you want to check out in other sessions that are, you want to chat and talk with the, the instructors, the speakers there, and then you're going to come back to us, right? Or go over, check out the interview. So the idea is you're hopping back and forth and throughout the day we're basically changing out every hour. >>We're not just changing out the, uh, the guests basically, but we're also changing out the topics that we can cover because different guests will have different expertise. We're going to have some special guests in from Microsoft, talk about some of the cool stuff going on there. And basically it's captains all day long. And, uh, you know, if you've been on my YouTube live show you, you've watched that, you've seen a lot of the guests we have on there. I'm lucky to just hang out with all these really awesome people around the world, so it's going to be fun. >>Awesome. And the content again has been preserved. You guys had a great session on call for paper sessions. Jenny, this is good stuff. What are the things can people do to make it interesting? Obviously we're looking for suggestions. Feel free to, to chirp on Twitter about ideas that can be new. But you guys got some surprises. There's some selfies. What else? What's going on? Any secret, uh, surprises throughout the day. >>There are secret surprises throughout the day. You'll need to pay attention to the keynotes. Brett will have giveaways. I know our wonderful sponsors have giveaways planned as well in their sessions. Uh, hopefully right you, you feel conflicted about what you're going to attend. So do know that everything is recorded and will be available on demand afterwards so you can catch anything that you miss. Most of them will be available right after they stream the initial time. >>All right, great stuff. So they've got the Docker selfie. So the Docker selfies, the hashtag is just Docker con hashtag Docker con. If you feel like you want to add some of the hashtag no problem, check out the sessions. You can pop in and out of the captains is kind of the cool, cool. Kids are going to be hanging out with Brett and then all they'll knowledge and learning. Don't miss the keynote. The keynote should be solid. We got changed governor from red monk delivering a keynote. I'll be interviewing him live after his keynote. So stay with us and again, check out the interactive calendar. All you gotta do is look at the calendar and click on the session you want. You'll jump right in. Hop around, give us feedback. We're doing our best. Um, Brett, any final thoughts on what you want to share to the community around, uh, what you got going on the virtual event? Just random thoughts. >>Yeah. Uh, so sorry, we can't all be together in the same physical place. But the coolest thing about as business online is that we actually get to involve everyone. So as long as you have a computer and internet, you can actually attend DockerCon if you've never been to one before. So we're trying to recreate that experience online. Um, like Jenny said, the code of conduct is important. So, you know, we're all in this together with the chat, so try to try to be nice in there. These are all real humans that, uh, have feelings just like me. So let's, let's try to keep it cool and, uh, over in the Catherine's channel be taking your questions and maybe playing some music, playing some games, giving away some free stuff. Um, while you're, you know, in between sessions learning. Oh yeah. >>And I gotta say props to your rig. You've got an amazing setup there, Brett. I love what your show you do. It's really bad ass and kick ass. So great stuff. Jenny sponsors ecosystem response to this event has been phenomenal. The attendance 67,000. We're seeing a surge of people hitting the site now. So, um, if you're not getting in, just, you know, just wait going, we're going to crank through the queue, but the sponsors on the ecosystem really delivered on the content side and also the sport. You want to share a few shout outs on the sponsors who really kind of helped make this happen. >>Yeah, so definitely make sure you check out the sponsor pages and you go, each page is the actual content that they will be delivering. So they are delivering great content to you. Um, so you can learn and a huge thank you to our platinum and gold authors. >>Awesome. Well I got to say, I'm super impressed. I'm looking forward to the Microsoft Amazon sessions, which are going to be good. And there's a couple of great customer sessions there and you know, I tweeted this out last night and let them get you guys' reaction to this because you know, there's been a lot of talk around the covert crisis that we're in, but there's also a positive upshot to this is Cambridge and explosion of developers that are going to be building new apps. And I said, you know, apps apps aren't going to just change the world. They're gonna save the world. So a lot of the theme years, the impact that developers are having right now in the current situation, you know, if we get the goodness of compose and all the things going on in Docker and the relationships, this real impact happening with the developer community. And it's pretty evident in the program and some of the talks and some of the examples how containers and microservices are certainly changing the world and helping save the world. Your thoughts. >>Yeah. So if you, I think we have a, like you said, a number of sessions and interviews in the program today that really dive into that. And even particularly around coven, um, Clemente is sharing his company's experience, uh, from being able to continue operations in Italy when they were completely shut down. Uh, beginning of March, we have also in the cube channel several interviews about from the national Institute of health and precision cancer medicine at the end of the day. And you just can really see how containerization and, uh, developers are moving in industry and, and really humanity forward because of what they're able to build and create, uh, with advances in technology. Yeah. >>And first responders and these days is developers. Brett compose is getting a lot of traction on Twitter. I can see some buzz already building up. There's huge traction with compose, just the ease of use and almost a call for arms for integrating into all the system language libraries. I mean, what's going on with compose? I mean, what's the captain say about this? I mean, it seems to be really tracking in terms of demand and interest. >>Yeah, it's, it's a, I think we're over 700,000 composed files on GitHub. Um, so it's definitely beyond just the standard Docker run commands. It's definitely the next tool that people use to run containers. Um, just by having that we just by, and that's not even counting. I mean, that's just counting the files that are named Docker compose Yammel so I'm sure a lot of you out there have created a gamma file to manage your local containers or even on a server with Docker compose. And the nice thing is, is Docker is doubling down on that. So we've gotten some news recently, um, from them about what they want to do with opening the spec up, getting more companies involved, because compose is already gathered so much interest from the community. You know, AWS has importers, there's Kubernetes importers for it. So there's more stuff coming and we might just see something here in a few minutes. >>Well, let's get into the keynote. Guys, jump into the keynote. If you missed anything, come back to the stream, check out the sessions, check out the calendar. Let's go. Let's have a great time. Have some fun. Thanks for enjoy the rest of the day. We'll see you soon..