>> Voiceover: Live from Austin, Texas, it's the CUBE. Covering DockerCon 2017. Brought to you by Docker in support from its ecosystem partners. >> Hi I'm Stu Miniman here with the final wrap with Jim Kobielus at DockerCon 2017. The CUBE's really excited that we were here for the third year. Have to have a big shout out to our partners and our sponsors that allow us to be here. Of course, Docker's been a great partnership. They talk a lot about ecosystem, really bringing some media people like ourselves giving us some of the great speakers from their company, the partner ecosystem and their customers, and the sponsors for the show, for ourselves, App Lariat, CISCO, Iguazio, Skelety, Cononical, and Red Hat. Without them we couldn't bring you this programming. Really excited to be able to be here. They're starting to tear down the show here, so not a lot of time, so many things to dock to. >> The show itself is containerized. >> We're not even going to be able to talk about the Franklin's barbeque. >> You just did. >> But Jim ... Absolutely. Jim, you've gotten to be on the CUBE here, see some of the show. Give us your quick hits. >> Sure. >> on your takeaways from the show. >> First of all, my first takeaway is this is a vibrant developer ecosystem, clearly. This show is much larger than the year before, and the year before that. It'll probably be twice as large next year. That's my prediction based on the sheer amount of developers migrating into the Docker ecosystem because so many organizations are Dockerizing their applications, containerizing their applications. That's a huge focus for me and Wikibon, as an analyst, is the containerization of application development with microservices and all that, for cloud deployment and multi-clouds, hot, hot, hot across all niches. So, vibrant ecosystem. Docker as the core solution-provider and the centerpiece of this community. Amazing show. The Enterprise Edition, of course, that preceded the announcement of that and the release preceded this show. That's critically important in getting Docker into new accounts that, with a full stack. Clearly it's enterprise ready. Developers, more developers will be exposed to Docker through the EE. Docker, at this show, had a couple of really important announcements for developers. Moby. Project Moby, for customization of container images and so forth, clearly that's going to be a multiplier effect on the ecosystem of developers, ISVs and so forth, Building applications, and customizing containerized Docker applications and images for a wide range of opportunities. >> Yeah, Jim, just want to comment on the Moby piece here 'cause it was really interesting. I think the last couple of years, it's been that pull and tug as to what was the open-source piece, what is the company itself doing, and I think it's clarifying. Kubernetes is a big rising tide in the environment, and all they cared about is they've got the open-source pieces that they need to be able to do Kubernetes. So, with Moby Project it's like okay, now I understand what's out and open. I understand what Docker's doing. I saw some humility from Solomon Hykes, talking, it's like we're listening. We're working, you know, ecosystem, ecosystem, ecosystem. So it was good to see that maturity. I mean, there were some people that I talk to, and they're like, "Oh, will this be the last DockerCon?" I'm like, "I don't think anybody watching this show would say that coming out." As you said, I expect the show to grow; it's doing really well. >> Solomon's totally partner-focused. Look at him. >> Kudos to what they're doing. The partners are excited. It's not just lip service. "Oh yeah. We did some little announcement on the side." No. We're excited. This is there. I know you've got a bunch of pieces, but I want to ask you, are developers excited about taking this legacy ... >> There's lots of news I'm going to analyze. >> Legacy applications, and like helping to move those in, or they only want to work on the cool new stuff? >> Oh, that's a huge theme. MTA. I forget what exactly the acronym stands for, but it's wrapping legacy applications, containerizing them in the Docker ecosystem. That is so important so all of these legacy applications will be Dockerized before long, and refactored, in addition to all the Greenfield development of containerized applications. So the MTA announcement, just as critical as the Moby announcement and so forth in terms, and EE as part of the show, of getting Docker, getting their ecosystem, getting developers working in this environment, more and more developers. This entire Docker, this entire ecosystem has a magnetic force on the developer community, or will. Those are very important. Also I thought the announcements with Microsoft, in terms of containers are going into Windows in a larger way, Linux containers and so forth, that also, 'cause Microsoft has a huge presence obviously in not only enterprise but small to midsize businesses. We're going to see Docker in ever-smaller deployments, hosts and so forth, across the board. More buyers, in other words, more companies will be Dockerizing more applications thanks to, in part, Microsoft as clearly a forerunner. >> Jim, absolutely. I say it at almost every cloud show. I want to follow the data and I want to follow the applications, and you had Microsoft and you had Oracle. You had two of the big players from an application standpoint, Oracle's now in the Docker store. >> Oracle's in the Docker store. That is huge. >> Yeah. >> That has validated containers and Docker for ... >> How about you? From the data standpoint, I heard, we talked to Iguazio about some of the analytics and things ... >> Jim: I'm a data guy, yeah. >> Yeah, you're a data guy. What's a data guy think at a show like this? Is it too infrastructure-focused, or did you see some of the data future here? >> No. It's infrastructure-focused in the sense that it needs to be to harden this technology for enterprise deployment, but it's really dev-ops focused, you know, Kubernetes and everything, and Swarm and whatnot. Look at all these vendors. Here are these tools for the dev-ops life cycle, Kubernetes and everything. That's really, really important. It's all about developers and speeding of development, and putting containerized Docker applications and images into production, and managing them and securing them and so forth. Just the sheer range of dev-ops tools on this show floor that's packing up now was amazing. I'm just uncracking my research here. Very important. So I'm going to wrap up. So, the adoption is amazing. I mean, all these industries, including like Visa. We had a swap-meet, who have adopted Docker into core applications that they're running major businesses on. That's some serious validation in its own right. >> Jim, one of the feedback I got from, it was actually John White from Expedient. >> Okay. >> talked about, and he said he deals with kind of small to mid, to little bit large enterprises, and he said, all that this keynote reminds us of AWS Re:Invent a couple of years ago. >> Oh yeah. >> Big global names. I mean, it's, you know, Visa. You know. Around the globe. Northern Trust. These are not, you know, your regional companies that did a little initiative. It's virtualization started in a lot of small environments. Containerization really started in the likes of Google. I remember the first DockerCon. It was Google and Facebook, and they're the ones that have been doing these projects pre-Docker, and it's slowly moving down. Part of the things I look at is where's the watermark >> Jim: Yeah. >> Where below this you're probably not going to do containers because you're going to go live on a platform that leverages container. The service writers I talked to ... >> Jim: They're going to live in a public cloud like Microsoft, or you know. >> Stu: The cloud guys. I'm going to go to, right, I'm going to go to Microsoft. I'm going to go to Oracle. >> Jim: AWS or IBM. >> Stu: I'm going to go AWS. >> Jim: Whoever it might be. >> Right. Any of them because they're going to just take care of that, and I won't care that it was containerized, so at the end of the day, it's not that tool, it's the wave of that modernization. >> Oh. Yeah, I want to end on a data note because we were talking about data. Okay. I thought Iguazio, I thought Yaron was very, that was very good to have him. There's a lot of storage foundations like Veritas and so forth, so storage in a Docker environment and persistent storage and data protection, pretty important, but also containerizing the new wave of applications that are machine-learning and deep learning and artificial intelligence. We got a fair look at some of that from Solomon yesterday because Solomon mentioned that the open AI consortium is based in their internal test bed training network on Docker, on Swarm and so forth. I, in my prior life, I just joined Wikibon a few weeks ago, I've focused on data science, which is a key development theme, by the way, I'll focus on for Wikibon. I saw a lot of containerization. I saw a fair amount of Docker and a lot of the data science oriented app dev that was going on in the business world. That's going to be a huge theme for me under Wikibon, but also, I mean Solomon sort of alluded to a lot, and so did Yaron, a lot of the work that's going on in the AI community Dockerized their application. Tenser flowing, all that. Huge theme we'll probably see much more of at next year's DockerCon I predict containerizing AI. >> All right. Well. >> For deployment into autonomous vehicles. Whatever. >> Jim, you've long been a CUBE alumn, but now you are a veteran of doing the CUBE. I really appreciate you coming on. >> I'm on this side of the table now. It's amazing. >> Stu: I want to give a shout out to the whole team here. John Furrier, I know, was really disappointed. He loves this show. Usually my co-host. A lot of these open-sourced shows. John, you better be down here in Austin for CUBECon at the end of the year with me. So many shows now through July 4th. The CUBE has so many activities going on. If you go to theCUBE.net, you can see all of our upcoming shows. Always watch us live. If we're not at the show that you think we should be at, go ahead and Ping us. Reach out to us through Twitter or through the website. Jim's research, a lot of it's going to be on Wikibon.com. Siliconangle.com is also where we have some research corner, some of the other pieces there, so check out the whole SiliconANGLE Media for Jim, myself, Ava, Leonard, Brandon, Jay, Sam, who's already heading to the airport. Thank you so much for watching The CUBE. Hope to see you at lots of shows coming around and thank you for sharing.

>> Narrator: From Austin, Texas, it's theCUBE. Covering DockerCon 2017. Brought to you by Docker and support from it's ecosystem partners. >> Hi, I'm Stu Miniman joining with my co-host Jim Kobielus. We're here with theCUBE at DockerCon 2017. When I talked to John Furrier, he said Stu, at DockerCon, we're going to get Solomon Hykes, the founder. We're going to get Ben Golub, the CEO. And we're also, of course, going to get Marianna Tessle, who is the EVP of Strategic Development. Marianna, thank you for having us back again, we've been having a great event. How is everything with you? >> Thank you first of all, it's great. This is the second day of DockerCon. I think we had a great set of announcement yesterday, and an amazing set of announcement today as well. It's really going great. You know I have been roaming the exhibit hall, and actually a couple of people said this is one of the best shows they have been part of, and this very engaged audience is great to hear. >> From the keynote yesterday, the word that stuck out to me is really scaling. We talk about scaling employment, scaling the ecosystem, and the show itself. I was at that first DockerCon when we were wedged into that hotel room, as Ben joked. We had 100 more people than we told the Fire Marshall. Because it was tight. TheCUBE is usually a little bit smaller footprint than we have at some other shows. But, Austin, first of all, you pick great locations. I mean, San Francisco, Seattle, here. I'm looking forward to... Have we announced yet where next year's is? >> I don't think we've announced it yet. Usually it happens in the afternoon. >> Here in Austin. Talk to us a little about some of those announcements and stuff that you're excited about with growing the ecosystem. >> You know, I'm going to continue the theme you started with scale, and obviously like you said, a lot of things are changing, and scaling. One of the things we have noticed more and more are companies and enterprises have really started to use us more in scale and more in production, more apps, more of that going on. One of the trends we've noticed that actually Ben covered on stage today is that there's not just the leading edge of development and all new apps, web apps, but actually, we are starting to see more of traditional apps coming on board as well. More traditions Ops saying, I want those benefits as well. I do not want to go all the way to the extreme of re-writing my code, and going to microservices. But I can reap a lot of the benefits from Docker rising and putting our tools on top. So we're actually seeing more and more of that. And more and more companies. >> The discussion with Solomon, we talked this morning. He said, Oh, I don't know what Lego set we are. And I said, You know that green, flat piece that you can build everything on top of, so you can have your spaceset, your castle, and all the pieces there. You want to be a platform that can build. One of the announcements you guys had today, it's the modernized traditional applications. Maybe you can walk us through a little bit what that means, you know that mix of microservices verses traditional apps. How you guys see yourself participating in a customer's journey. >> Right. So, when we call this program, by the way it has a nickname, MTA. It's like you said, what we've seen is customers and users that want to have benefit across the board was if they write new code as they have more traditional apps with traditional stacks. What we came up with is a way for you to move from a more traditional to the new and Dockerizing really quickly. One of the things we also announced today, is a go-to market and a program helping customers to do that. We have great partners we announced today and I'm sure we're going to have even more, whether it's Microsoft, Avalon, HPE, and Cisco. What we're going to basically provide is a way for you to very quickly start seeing the benefits. Taking the traditional app, and within days, like five days, you should be able to get it in a modern state and start seeing the benefits from that. It's something that we're going to encourage customers to do very quickly and see the benefits. In fact, we had a customer today, Noran Trust, who's already been doing that, talking about the benefits they've been seeing from this program. >> Marianna, in terms of developer enablement, that's everything to getting Dockerizing, a universal phenomenon for wrapping legacy systems, for refactoring existing code, for building greenfield applications. What will Docker do to continue to improve the experience of Project Moby as an enabler of your ISV ecosystem? Going forward, how do you see the experience of front-end in front of Moby evolving to enable very simplicity and speed of development? >> First of all, I have to say that one of the magic, or secret sauces of Docker is our user experience, and the way we made technologies sometimes that were already available super accessible and super useful for developers and ops and users. So I would say that's definitely something that we have the DNA to do. And a project in Moby, we see ISV's and companies, and it doesn't have to be a company, it could be like users, a company that can come in and collaborate and really create a new component, or a new project from what we're going to put there, and hopefully others as well is a whole set of these Lego building blocks they can assemble. >> Are there any plans of Dockers to provide task-oriented skins or experiences on Moby for different roles, different developer roles associated with particular projects, you know, task, or wrapping a legacy system is a different task, obviously, from developing a greenfield containerized application. So to an extend, will you evolve the tool to enable more task oriented role specific interfaces? >> I would say as far as Moby, and across the company, we do have this realization that it could be that developers started to use Docker first, but actually Ops, and even like we talked about, traditional IT, it's pretty prevalent. So our thought is really to cater to all of these audiences, kind of understand, have a conversation with them and understand what exactly they need and what would make them more productive. An example of what I mentioned with the MTA program, the Modernized Traditional Apps, that one is targeted more towards an Ops audience. Different things we do, we try to understand our audience and engage with them, and see what's going to make them most productive. Both in terms of tool sets and in terms of how we bring it to them. >> Right, right. >> Marianna, we had the opportunity to have some of the partner keynote speakers on theCUBE, John Gossman on from Microsoft yesterday, we had Mark Cavage on from Oracle, here. There's a lot going on. Maybe give our audience a little flavor as to some of the other partner activity going on that we might have missed if we weren't watching close. >> I think we had the same conversation last year, just explaining how important it is for us that we work well with our ecosystem. It's a big part of our plan and strategy, and again confirmation that customers want to use choice, different things, that we're not alone in the world, and we really want to engage with a vast ecosystem. So you saw from Cloud providers to a more on-prem infrastructure to ISV's to networking providers, storage providers. Like a whole understanding and way to be a full platform, we really need to understand how to integrate and how to engage with that ecosystem, and how to help customers have benefits of the entire thing combined. So we've been really looking at who are the different leaders; Sometimes customers take us there, they're like, hey please partner with this company or that company. Understanding mapping of what is needed, and starting from Cloud, infrastructure, network, storage, management, monitoring, security, all the way to ISV's. I would, since you brought up that fact that Mark was here, Mark from Oracle. I do want to talk about that because I think that is maybe even a bit new and unique. Another thing that we announced today, the fact that we have Oracle, Dockerizing their apps and putting them in Docker store and that is big, and again, to us that is obviously big, but again, big for user. It's a very easy way to get software you really need. And not only that, we announced several weeks ago, a certification program. The nice thing about that, if something is certified in store, you can really use that with a lot of trust. You know it's been tested, it's secure. That we made sure that it followed best practices. We made sure that our support engagement with the publisher. Again, geared toward enterprises that really want to have that confidence of downloading something from the store and just using it. Again, Oracle is kind of groundbreaking in putting their software there, and we're very excited about that and we think there is going to be more to come. We really are looking forward to this being an amazing service for our users who want to really start from components that exist and the components that they can trust and be productive very quickly. >> I'm curious, how do you think of the Docker store in relation to things like the Amazon Marketplace, or you know, many of your other partners have their own piece. There really is no kind of enterprise app store today so what do you guys want to own? How do you integrate with partners as you look at that develop over time? >> For us, Docker Store started as an enabler as we saw more and more need from users to to basically, Hey, I want.. Let's say since I talked about Oracle I want to use a database. I don't want to go and Dockerize it again. If somebody already did it and they're already prepared, they already went through it, why wouldn't I just re-use it? So the fact that you can put things in this building block and then move them around, it actually enables the idea that you can re-use the same component between different users. So basically you have here something you can do once, and many people can benefit. So that's the benefit we see. It started with official images long ago. We saw unbelievable traction for it. Users really love it, it makes them productive very quickly. We wanted to expand it to a wider set of ISV's, a wider set of components, a wider set of apps, and make them available. We, right now, see it as more of an enabler and again it's one of those things, listening to our users, listening to our customers, we saw that that's one of the things that will make them productive really quickly. >> One of the things we saw in abundance at DockerCon this year is customers of Visa, MetLife, and so forth, up on stage, talking about how they are using Docker in their business for actual live applications. In terms of partners, are you focusing on particular vertical industries in terms of partnership with ISV's and VAR's, particular geographies? Give us a sense for where you're going in terms of diversification of geographies and industries, and in terms of your focus on partnerships. >> Yeah, and again different parts of the stack require different kinds of partnerships. Like on the South end of the stack on the infrastructure, we're looking for partners that either provide on-prem or Cloud infrastructure, or they can provide a set of plug-ins that integrate with us and a set of tools that can be used with Docker to complete and enhance the overall experience of users using Docker. So that's kind of one set of partnerships that started from hardware vendors, to different plug-ins. On the North side of it as we look at it, we just talked about the fact that we have... >> Jim: Top of the application, the application services end of the staff is the North, right? >> Exactly, and all the way to the content. What you actually put inside and what you run. >> Data, so forth and so on. >> Exactly. We'll form a set of partnerships there and making sure that those components are available in store, those components are Dockerized, that companies can really use that, and obviously Microsoft is a huge partner for us in the OS and as your others as well. >> The storage vendors, like Veritask and so forth, there is a fair amount of data inside the ecosystem that really you're going to continue to develop a partnership. >> Absolutely, Adera, Quadera, you've seen a lot, and we continue partner and seeing what's needed there. Understanding we are trying to predict where customers are today, where they're going to maybe, what they will need a year or two from now, and be ready for that. >> Marianna, that leads me to my final question. We know where you're going to be in Europe, you won't tell us yet the location of the North American show for next year, but as you look at the ecosystem, how do you see that developing? When we sit down with you a year from now, what do you hope to have as the progress? >> As I look at the exhibit hall, I am hoping that we're going to see a bigger exhibit hall with every single DockerCon. And, not just for fun, but really, it kind of indicates the collaboration we have with the ecosystem. I would like us to be known as a trusted and productive partner for our ecosystem. And a trusted and productive partner for our customer. That kind of knows to work together with all these contingencies to have amazing results. Like you said, we seen customers on stage, we seen the press releases of people say it took me months to get VM going, it takes me seconds to get this now going. So you see the kind of productivity and we would like to enhance it even more and get there faster. >> Absolutely, Marianna, always a pleasure to catch up with you. We've got a few more interviews left, two days of live coverage, for Jim Kobielus, and I'm Stu Miniman. Thanks for watching theCUBE. [techno music]

(upbeat electronic music) >> Announcer: Live, from Austin, Texas, it's theCUBE, covering DockerCon 2017. Brought to you by Docker in support from its eco-system partners. >> Hi, I'm Stu Miniman and welcome back to theCUBE's coverage of DockerCon 2017. Happy to welcome to the program one of the Keynote speakers from this morning. It's Mark Cavage who is the Vice President of Engineering with Oracle, and, also joining, is Sidhartha Argawal who's the Vice President of Product Management and Strategy, also with Oracle. You've been on the programs a few times, thanks for joining us again. And Mark, thank you for joining us for the first time on theCUBE. >> Absolutely, glad to be here. >> So, you know, one of the topics we've been talking about, this week, is kind of the maturation of what goes on in containers, and the thing that jumped out at me is, you know, we talk about all the use cases, some of the cool things you're doing, it's like, "What applications do I run in containers?," pretty much all applications that I'm running. And, I've said, the stickiest application that's out there today is the one that your company does. You know, you talked about the Database, talked about some of your products. You know, Oracle, very well known as to kind of where your applications do. So, you know, on the Keynote this morning, I mean, there was actually like a pretty good round of applause talking about your announcement. So, Mark, let's start with you as to the announcement you made, you know, partnership with Docker. and what's happening. >> Sure. Yeah, no, absolutely. Honestly, like we're really thrilled about it. We're really excited leading up to this. You know, as I say, or as I said, there's a few people that know about that Database and know about Java. So, we got a lot of people using our apps. You know, we've been working with Docker for a few months. It's a great partnership. As we, you know, kind of announced in the partnership, or in the Keynote, sorry, you know, we put out basically everything that's important, right. So, we started with the bedrock software that people are using to build all the modern or their traditional, mission-critical applications, they're now modernized. So, database, WebLogic, Java, Linux, that's all certified now in Docker. So, it's a big deal for us. We're really happy about it. >> Great, it's interesting to hear. It's like, "Oh, we've been a great partnership "for a few months." I mean, you know application development, you know, is like decades it takes for things to change. Talk about how this fits into to kind of overall strategy, the platforms you build, and what's happening at Oracle these days. >> Yeah, I mean developers are wanting to leverage the Oracle content in the containerized format so that they could easily, for example, not have to worry patching, upgrading, et cetera. They could easily move those into production. So, what we're doing is we're connecting a lot with developers by having a series of events called Oracle Code Events where these are free events where we inviting developers to come. The topics are containers, microservices, dev-ops, chatbots, machine learning, and it's not about Oracle delivering all the sessions in those events. We opened up a call for papers and in three months we got 1800 submissions for external speakers to deliver sessions. So, it's about a 50-50 split between external speakers and internal Oracle speakers talking about all exciting, sort of, areas in dev-ops, in containers, in microservices. We created a developer portal so developers can go to that portal and, from Oracle, get access to all the assets that are there. We're creating a Oracle Champions program, called Oracle Gurus, so that people who really good, who really want to be blogging and talking about content, they can get recognized by Oracle. So, we're doing a lot to connect with developers. >> That's great. And, you know, in the Keynote, you talked about this is free for test and dev purposes. Got to ask you about, which probably your favorite question, though, is, you know, the audience... You know, I looked on social media and it's like, "All right, what does this mean "when I containerize from a licensing standpoint?" We've all seen kind of, you know, cloud pricing models, if it's, you know, Oracle versus if I'm using, say, AWS. So, what is the licensing impact when we go to a containerized environment? >> I know, honestly it's not any different than we are today, but, you know, we'll be clarifying it over the next couple months. >> Stu: Okay. >> As I said, we'll be iterating a lot with Docker Store and all their software catalog we put out there. It's, you know, stay tuned for more. >> And I think the one thing to add is that, you know, the key benefit that developers get is, for example, if they go to Docker Hub today. You have 80 different images that different people have put up for WebLogic or for Oracle Databases. You don't know which one you want to use, right. But, when you come to Docker Store, Oracle has certified the images and put those images up. So now, you can get support from Oracle. It's certified by Oracle. And then, if you report problems, Oracle knows which images to fix or what problems to fix as opposed to some random images that might be there on Docker Hub. >> Yep. >> Yep. >> Yeah, that's been a real problem, so it's a big deal. >> Yeah. >> So, we've seen a lot of diversity as to how users can consume the applications. Maybe, give us a little insight as to how things are going in Oracle. I mean, you know, you've got your staff, you've got your cloud, you know, we talked about containers here. I mean, it's, you know, rapid change in something that, you know, overall, I mean, the application they're using doesn't drastically change overnight. Consumption models. >> Yeah, no, you know honestly the company's been going through a huge transformation over the last few years, as I'm sure you've been told, as I'm sure Sidhartha has told you. You know, we're actually containerizing ourselves, internally, across the board. Almost all the new PATH software we're building, almost all of the new IS software we're building, we're building towards that. All of our PATH software, all of our IS software, we're going pay by the hour, fully metered, fully usage-based pricing. >> So, you know, we want to make sure the people can consume in a subscription based format, and it goes across application development, cloud services, across Integration Cloud Services, analytics, management from the cloud, identity, et cetera, everything is on a subscription basis and we're also enabling this on-premise. So, there's developers who work at financially-sensitive companies that have compliance issues, or that work in companies within countries that are data residency issues, and they're unable to benefit from the rapid innovation that's happening in the cloud. So, we're actually providing that same subscription model in their data center. So, we ship an appliance, they start using the appliance, and we're actually delivering the service on that appliance. So, they could do dev-test in the public cloud, and then, you know, do production on-prem where they're meeting the compliance requirements, data residency requirements, and Oracle is managing that environment. You're not buying the appliance. You're actually buying the service just as you were buying it in the public cloud. >> Mark: And the pricing is identical. >> And the pricing is identical between public cloud and what you get delivered as public cloud in a data center, yes. >> One of the things, you know, those of us that watch Oracle for a long time. You know, people have the perception of what Oracle is. I've seen a number of, you know, really good people that I know, Oracle's hired over the last few years. Mark, I mean you were called one, you know, one of those rock star developers. You've got a really good pedigree from the some of the previous clouds. Give us a little insight as to what you see from an engineering culture, you know, architecturally standpoint, you know, is this the Oracle... That, when you joined Oracle, is this what you expected? You know, what's it really like inside? >> Yeah, honestly, as I said, really the company is changing across the board a lot faster than people realize. And that's truth for both, you know, the rock stars that were already in the company and the rock stars that are coming into the company now. You know, you've interviewed the Seattle team before about some of the cloud up there. We've brought in several hundred people from outside companies, from, you know, really strong pedigrees, right, Googles, Amazons, Microsofts, et cetera. We've done a ton of hiring in the Bay Area. We've brought in a lot of start-up talent. We've done, you know... There's been, of course, a few acquisitions. We bring in really solid teams, and then, honestly, just the culture, itself, is changing. Really, you know, transformation to a cloud company is, it actually impacts everything, right. It impacts the way you do support. It impacts the way you do development. It impacts the way you do operations. It impacts everything, so. >> Well, I think, you know, if you think about it, we're going from a company that built airplanes and sold those airplanes to others, for example, Boeing selling airplanes to Air France, et cetera, to actually becoming an airline where you're now not just building the airplane, you're actually flying the airplane, operating the airplane. So, in the Development and Engineering organizations, the engineers are understanding that they need to understand what the impact is on Operations of what they're releasing. They can't say, "Oh, send me the log files. "I'll log a ticket," because by that time it's affected many people. So, one, they have to create transparency into what's happening in production in real-time. Two, be able to respond and react to that in real-time. And the other thing that is a change in culture, both in Engineering and actually across the board including in Sales, is customer success. In cloud, people expect to get value in three months, four months, six months, et cetera. So, having a very significant focus on ensuring customer success within three to four months, right, then, they will renew their subscriptions. They will continue working with us. So, there's actually a very significant change in culture that's happening. And the other thing is, we're not just going after the large enterprises that used to be the bread-and-butter for Oracle, but now we also have small-medium businesses, start-ups, et cetera, saying, "Hey, if I don't have "to worry about installing, managing, configuring, "Oracle Databases, Oracle content, "I can just go use the capabilities that are being provided "by Oracle and pay for it as a subscription." And so, we're really shooting towards developers realizing that the Oracle cloud platform is a open, modern, easy platform. Open, because they have a choice of programming languages, Java, SE, PHP, Ruby. Open, in terms of database choices, not just the Oracle atabase, but MySQL, Cassandra, MongoDB, and Hadoop clusters, and open in terms of choice of deployment shapes, right, where you can have VMs, you can have bare metal, you can have containers, or you could have server-less computing. >> Yeah, you brought up speed. You know the pace of change is just phenomenal. I think about the traditional kind of software life-cycles versus, you know, where Docker is today. I mean, you used to go from 18 month down to six weeks. So, kind of a two-part question. How are you guys, internally, managing that pace of change? And, how are you helping your customers, you know, manage that pace of change? You know, Docker has the CE and the EE. So, you want to be more bleeding edge, everything else, or do you want something that's a little more stable? How do you guys view it internally and externally? >> Yeah, no, that's a great question. Certainly, internally, we're, you know, we're as bleeding edge as... We just talked about this a second ago. You know, we're moving fast. We're shipping software every day. The interesting thing, I find, is actually customers are going through the same transformation. And, most people don't realize when they go to microservices, actually, it's a big organizational change, right. Like, it changes the way that you have to structure your team. It changes the way they communicate with each other. And so, honestly, you know, a huge part... To the previous question, a huge part of this for us is, we need to be doing this because our customers are doing it too, right. So, we need to have empathy. So, we're doing that. >> Well, and I think, in terms of speed, you know, previously Oracle might release on-prem software once every 12, 18, 24 months. Now, I'll give you the example of the Integration Cloud Service. We've had four releases of it, four to five releases of it within a year. So, you know, the rate at which we've actually getting the releases out, getting the content out, means that customers are getting innovation much faster. And also what we're doing is, we're taking input from customers on the releases that have happened so that we're actually prioritizing the input that we're getting plus the roadmap that we've set up to say, "Hey, what should we be working on next?" So, our roadmaps are actually changing inflight. So, it's not like you set the roadmap for the next nine months or 12 months, but you're actually saying, "Hey, but this is the input we got, "and we need to deliver faster," you know, or, "We need to deliver a different set of capabilities "within that same time frame." And I think customers are now getting used to the fact that if they didn't have to get the new build, install the build, manage, configure, make changes, et cetera. They're saying, "I just got the new capabilities. "My application still works "and now if I want to use that capabilities, "I can start leveraging it," right. So, for example, orchestration was added to the Integration Cloud Service. They didn't have to do anything to their existing integrations but now they could use orchestration for more complex integrations if they wanted. >> Yeah, want to give you both a final word on this. Either, you know, conversation you've had with, you know, a customer or partner, or, you know, key takeaway you want to have people beyond what we've covered already. Mark? >> Yeah, no, you know, honestly, I really said it this morning in the Keynote where we really are focused on developers. Developers really are driving decisions these days. We know that. This announcement from us, with Docker, was the first of many things you're going to see. We absolutely committed, so stay tuned for more. >> Mark: One more developer and will, will, will... >> Oh yeah, you told, you warned me about that. >> Yeah, absolutely, Sidhartha. >> I think that, you know, what we've heard is developers are surprised when they find out the capabilities we have to help them build microservices, container-based applications. Being able to have a run time for microservices, being able to have API management for all the API services and microservices, being able to have a monitoring management infrastructure from the cloud so they don't have to install it and having a CI/CD pipeline all provided to them as a service in the cloud, wonderful, that's the feedback that we've gotten for those who've come and tried the Oracle cloud platform. >> All right. Sidhartha, Mark, thank you so much for joining us, giving the update. Congratulations on the announcement today. Know a lot of people will be checking out the Docker Store to understand that is, yeah... Well, we'll have to talk sometime about kind of the enterprise app store, in general, and where these all live, but we'll be back with more coverage, here. You're watching theCUBE. (upbeat electronic music)