 Great to be here. So, a little experiment today. I thought instead of doing an extensive series of slides and theses and observations, I might just do what Josh and I normally do when we sit around my office on Friday night and just talk about the patterns that we're seeing out there, how it's informing our strategy and what we're seeing in the market, the trends, and what this is really all about. So, hopefully you don't mind coming along with us on that journey while I grab the clicker. Oh, yeah. Don't forget the clicker. So, Josh, you came to us last fall, was it now? Yeah, October, I think. And you've been on the road pretty extensively, and you came in with a pretty unique perspective of someone who'd been focused on infrastructure, had always wanted to build a platform. What's it been like living on a plane speaking with all the largest organizations in the world? So, I stopped counting cities six weeks into the year because it was starting to freak me out. But what's really amazing about this transformation is it's not a single industry. You know, I'm working now with financial services, federal government, industrial, retail, automotive, insurance, medical. Like, it's every industry, every vertical in every region. And what do you think is common across all those diverse sets of economic organization that you're seeing today? What are the uniting themes, technologically, organizationally, that you see as you walk into random meeting rooms in every state in the country, in every region around the world? I mean, I've decided to call cloud-native the meme that binds. Yeah. Because different organizations will have other things they talk about. Maybe they have a CD initiative, or maybe they're trying to get more agile across the business. But this idea of a fundamental architectural shift is totally ubiquitous. Actually, I was going to tell a tiny story. James wants me to keep on the clock, so I'm going to immediately ignore the clock and tell a story. You know, I started programming when I was six, never went to college, and so my first really professional programming job, I had no idea what I was doing. I was like, I know how to write lines of code, and that will be good enough. So about a month into that, my good friend Chris Campbell handed me the gang of four book. And at the time, this was a total revelation for me. I was like, there's actually a right way to do this. There's this thing called architecture, and you can think about it, and it totally changes the game. And I feel like now the equivalent of going to college is working at Google. Yeah. And everybody who works at Google comes out of Google with this notion of, like, there are these patterns that you should use that change the game. And so, you know, Cloud Foundry and going out there with Cloud Native architecture is sort of like handing people the gang of four. Yeah. And all of a sudden they're like, whoa, we get it. I think that's the point that most resonates with me, like over the last year that's changed the most, is that it went from, you know, the first time I got on a plane did 40 cities myself last year, not as many as you. To start explaining this to people two years ago, it was pretty abstract. And what's really happened is that everybody has started to realize that Google isn't different from them, they're the future. Netflix isn't different from them, they're the future. Yeah. And that they have to close that gap somehow and fast to compete. Yeah. You know, people talk about Cloud Native as if it's only about scale, right? Yeah. And they say these giant scale businesses weren't Cloud Native because they had to for scale. Scale is not just about the number of users, it's about the number of transactions, the amount of value. And the amount of value is combinatorial out of the number of just different pieces you're pulling together. So in a large organization, connecting two or three systems, you suddenly have a scale problem. But it blew my mind when you said you came back from Washington, D.C. Just let's get very specific about this. You were in Washington, D.C. and an organizational leader said to you, we know that we're too monolithic, we know that we have to refactor to Cloud Native, maybe microservices, and we know that we need a platform. So it's not just one, I did nine agencies in 48 hours. Most of them three letter. Yeah. And they're all in exactly the same position right now. Yeah. They're like, our systems cannot be adapted to the changing world. We know this. Yeah. You know, we went to Agile, we figured out how to build a new release in two weeks. It still took us nine months to push it into production. That doesn't work. Yeah. And we know we can't fix the operational model without changing the application development model. And that's where they saw the Cloud Native application just playing right in. So it was every single agency I talked to had exactly the same agenda. Yeah. And it was amazing. Diego from the ATNF organization, the government yesterday had an awesome quote. And he said, let's just transition on this one. He said, it's obvious to me that Cloud Foundry is the future of enterprise DevOps. Yeah. Now what do you think he meant by that? Well, he also he quoted it slightly different. He's one of our developers when I asked him how they felt about the pilot. And pilot is a loose term because they went straight into production. Yeah. He said, you know, if you take Cloud Foundry away from us, we will hurt you. These are the small moments when you've been on this journey for four years working on this that you're like, maybe this will work out. Yeah. Yeah. The, you know, the difference is so, and government look, I worked at NASA, right? It took us six months to get a VM. It took 18 months to get the first system into production. The team can get an authorization to operate in three days. Yeah. I've never heard of a government agency doing that. I mean, that was the great game changing. That was the great thing. You know, in the same theme we heard from Andy Zittany yesterday of Allstate. He said, it used to take 100 days to do this. Now it takes 15 minutes or less. Yeah. And asking an unfair question. And this is what this quick notes about here is that there's a really revolutionary thing about Cloud Foundry in that it works. And that was one of the themes that I heard yesterday and all the customer talks said, hey, actually, this technology, we installed it, we used it. It worked as advertised as opposed to, I think, where they've been coming from, which was these two or three year organizational changes around, let's go build a platform and unite around that. They're now realizing that they can arbitrage between Google's capability and their own by using Cloud Foundry. Yeah. A lot of the other, the previous approaches to this problem space, you know, how do we make it easy to deal with distributed systems, have been either language specific, framework specific, or have required superheroes? Yeah. And there was a lot of discussion yesterday about superheroes and how we're all kind of, we're superheroes or we think we are, and that's super cool. And I believe it. I think we're cool. We wear hoodies. I don't. But ordinary people do not fly using a cape. They get on a plane. That's right. Right? And so Cloud Foundry is essentially a plane. It lets everybody fly. That's right. And that, I think, is really, really powerful. I think that's what's so revolutionary about it for me is that the idea that it's, you know, I talked to a leader at a major banking company who said, hey, we use some, you know, configuration management on top of OpenStack previously. And he said, what I really end up building was a snowflake generator. And what it's really connected with me and CIO is a simple question is like, why are you still managing operating systems? This is a simple question I ask. And Cloud Foundry embeds an operating system in it so that you're just managing at the application level, much like consuming an Amazon service, like a relational database service. You don't even know what the OS is. You don't need to. Yeah. Another segue, right? James was building Cloud Foundry when I was building OpenStack. Yeah. And my goal was to be building Cloud Foundry. That is what OpenStack was built for, was to get to the structured platform part. Because I don't really think hand tooling to an IaaS API is a long-term strategy for application development. And I think that's what's so amazing is that we've started to deliver really on the promise that this works. You can plug it in today. There's 10 Pivotal CF customers speaking here. I mean, this is not like in some of the other open source worlds where they're like, hey, when is Enterprise going to show up to the party? Like, Enterprise helped us start this party because the capability is already mature. You know, James, part of our job or your job in particular, my job is to go talk to people about what works today. Your job is to be ready for what they need in six months. Right. So most folks, when they say Cloud Native, they translate that into 12-factor. And 12-factor has become this amazingly powerful way of describing what a Cloud Native architecture looks like. But as soon as you actually do Cloud Factor, there's a new set of challenges that come out of that. Do you want to talk about going beyond 12-factor? I mean, the awesome thing about Pivotal is that we are also responsible for the entire spring framework community. And one stat I wanted to share with the audience today, because I think a lot of people are really stuck in legacy technologies like WebSphere and WebLogic. And it really clogs their entire organizational structure because they're like, hey, we got to get the WebSphere admin to do a deploy. And it's incredibly complex and they're scarce. And that whole continuous delivery Cloud Native architectural organizational change just grinds to a halt. And I showed one of these WebSphere guys one day how Cloud Foundry worked, and he said, I'm so mad I want to flip the table over. This is a quote. And you can see that anger coming out in this download chart of Spring Boot. Now, Spring Boot is what Netflix uses for their microservices Java. It embeds a very lightweight runtime inside of it. And you can see it went nearly vertical at the beginning of this year, which is another indication of Cloud Native adoption. So we had over a million downloads by developers of Spring Boot in April alone. Yeah, that's a really powerful stat. And you said Netflix like four times, right? And they are the poster child for Cloud Native architecture, probably mostly because Adrian has spent so much time explaining it to people. Well, what I admire about Netflix is they're built for speed and resiliency. Like everyone I talked to, you know, a major retailer was in talking with us and me and Rob me last week. And he said, how do we transform for speed and how do we get resiliency in everything that we build? One thing I admire about Netflix is they culturally turned that to 11. They said, how do we structure everything about our applications to get to 11 on speed and resiliency? And it's a great privilege that the Spring Team works directly with Netflix. They use Spring Boot. We also have this thing called Spring Cloud now, which includes all the Netflix microservices right in the Spring programming framework. So I actually want you to stop and say that over again because I went to... The rumor of this got out, right? And I was in... We're leaking it right now. I was in Wall Street. I was meeting with another one of these very large banks. And they stopped me in the middle of the presentation where this was like a footnote. I was like, I'm talking about Cloud Foundry. And they're, wait, wait, wait. You just said that we get all of Netflix OSS for free? Yeah. This happened again yesterday. It was out for some lunch meeting. Somebody was like, wait, we get Netflix for free. Conversations over. Let's just go. Let's go do that. I think it's so important because you start to bring the cloud native architecture, not just into the platform. The platform and infrastructure resiliency and team management, et cetera, like Cloud Foundry has with multi-cloud. But you also start to bring it right up into the framework. I get giddy when I see people writing Spring Code and it says At Histrix, which is a circuit breaker from Netflix, right in there, which provides resiliency and failover right in the application. What's going to happen is those are all going to be pivotal CF services as part of Cloud Foundry. So the platform and the programming are going to become one big blurred line for this cloud native architecture. It's going to be powerful. Yeah. So I mean, one of the big promises of Cloud Native is that it's not about where you run your app. It's about how you build your app. Do you want to talk a little bit more about how from a product strategy we've been addressing this? Yeah. Because I know it's a huge concern across all of these verticals is we don't want lock-in, right? And certainly the embrace around open source has been how do we stay away from getting married to a single vendor? Why not turn Bezos into Larry Ellison? I think in addition to that, the two big trends that I see out in the market right now are Cloud Native for organizational design, agile, app architecture, and then multi-cloud in terms of IT, because the CIOs don't want to get locked into Amazon. And they also don't want to get locked in the private data center because they know in two years that they might have to have an Amazon initiative and they don't want to get locked in the private data center. And I think one of the reasons Pivotal Cloud Foundry has been the most popular way of using Cloud Foundry in the enterprise is that we are so dedicated to multi-cloud. And I know you helped us recently with CenturyLink in terms of maybe tell folks how we're doing that integration and very dedicated to running on any API on any cloud. Yeah. So the CPI, the Cloud Provider Abstraction inside Cloud Foundry is probably one of my favorite things. I was at Piston and we pulled those two teams together to build the original OpenStack CPI. Yeah. And the work that the whole community has done in maintaining and expanding that, I know IBM's leaned in on that a lot. Yeah. CenturyLink actually looked at that and said, hey, why don't we just implement a compatibility layer of OpenStack APIs, even though we're not even running OpenStack, because that is the much simpler part of the process. Yeah. So that works really well. So I think that's the other big trend is the multi-cloud. And people really want multi-cloud choice and we've delivered that. The final proof point that we try to put into the product itself is that we've said our hosted services include in our software. And I think that's really a big proof point for us with enterprise CIO is because I said how can I afford to give you access to our hosted service for no more than a year? So I think that's the important part of that is saying we believe so much that cloud native architecture is efficient. We're going to take all of the efficiency gains out of our own bottom line. Like, it's, I mean, I think you're a little crazy. It's working. It's really working. But talking about like putting it on the line. I explained to them, well, it's containerization and efficiency of a cloud native platform is what allows us to give you just capacity on demand and we've been dreaming about this for five years. You were dreaming about it at NASA and it's great to see the variety of customers really that have come to this event and that we've assembled and the people that were helping. You know, as a closing thought, I got into an argument on Twitter a couple days ago. Again? Again, as usual. About the definition of prod. What does it mean to be in prod, right? And this has always been this magical benchmark of how do you know an open source project is mature is when it's used in prod. Most of the PCF customers I talked to went straight to production. Like this was not a concept of oh, well, we've got to do because that's what cloud native is. It says there is a single approach that allows you to go from dev to prod in one motion. Which it just it changes the game. You can't you can't have an idea on Monday and ship an idea on Friday if you have like nine months of workflow. Yeah, I think that gets back to the urgency that some people feel to implement and use the platform and get moving with it quickly. And you know, so just in summary and feel free to come up to Josh and I in the hallways and continue this casual chat. But to me cloud native is really about a change in the way organizations and applications are structured. It's the ability to run that application on the cloud of your choice without encumbrance to any local dependencies on that cloud. And finally, I think it's the ability to use a structured platform in the way that Google and Netflix have all built these very structured, very rigorous platforms to get incredible efficiencies and agility. No one has ever done cloud native without a platform. Either they've built their own or they've used CF. I think that's that's a really great thing to end on. Yeah, thanks. Thanks.