 I'm Ed Anna of Apigee, and I'm going to talk to you today about why APIs are important for multi-cloud. Now, a lot of folks today talking about multi-cloud, this is great for a long time. The conversation was about getting to the cloud, but getting to the cloud is not enough. We need to get to the clouds plural. And so you've heard that all afternoon and all evening, multi-cloud strategies and how Cloud Foundry is going to help you get there. And there's a lot of good reasons for this. Might be trying to turn your data center into a private cloud, creating the cloud-born enterprise, all of this good stuff. Maybe you just don't want a single source on a single vendor. You want to have other options and what have you. All good reasons to go to multi-cloud or to go to the clouds plural. Turns out that this isn't the first time that there was an ambitious project to get to the clouds. Some might recognize this, the Tower of Babel. Also an ambitious plan to get to the clouds. This project failed due to polyglot requirements. It was a monolithic architecture and fell apart when people couldn't agree what languages to use. Some people blame divine retribution. I blame it on hacker news. Some people felt you should go to Lisp. Other people were talking about server-side Swift. And they ended up throwing in the towel. I think we've all worked on IT projects like this. But the point was that building a project like this, you break it into teams. Teams choose their own communication styles, their own ways of working, and so on. There has to be a way to bring that all together. So what does this have to do with APIs? Well, your teams are building apps. And apps talk to each other via APIs. And left to your own devices, your teams are going to come up with their own API styles and so forth. Turns out that the problem with APIs isn't really about rest versus soap, regardless of what your integration folks or your API teams might be telling you. No matter how many debates you see on hyper-media APIs versus whatever. The real problems are what are called the non-functional API issues. And those are things like your security mechanisms, your documentation, your analytics, and so forth. These are actually the challenges that happen when you try to make your APIs consistent, work between apps. And really, when you look at the multi-cloud problem, it really is at its heart an API problem. So what's the solution to this? Well, some of you have probably have heard of API management as a category. I know many of you are running different types of API management software. In my zest to get up here, I forgot to introduce myself, Ed Anna, from Apigee. We do make API management software. That's why I'm talking to you about this today. But API management does seek to solve these types of things. And one way or another, you will solve these. You will need a way to either have common security authentication between all of your workloads, all of your apps that are exposing APIs. You can't have 10 different authentication schemes. You will need a way to document your APIs in a self-service way so that people can publish their APIs for others to use. And if you're consuming these APIs, consume them in standard ways. And you'll need a way to monitor these, get your analytics, and so forth, regardless of how you're publishing these. The good news is that within Cloud Foundry, there's now a capability called Route Services. And there's a number of good sessions that are on the conference agenda that I encourage you to attend to talk about what Route Services are and why they're relevant to APIs. But in a nutshell, what this is about is allowing you to plug into the Cloud Foundry Go router, intercept your HTTP traffic, in this case specifically your API traffic, and then doing all of these key requirements for being able to go and authenticate your APIs in a standard way, do good things like rate limiting them, and so forth. But the important thing here is that you want just the same way that Cloud Foundry makes possible for everyone, for all of your teams to do software right, to do their apps right, by integrating your API infrastructure into this, you're going to ensure that every team does APIs right. And doing APIs right means in a consistent way across all of your applications, because if your APIs are not consistent, if people can't learn how to use them, you can't secure them in a uniform way, it defeats the whole purpose of doing them. So with that in mind, your goal is don't let your infrastructure projects turn out, like the Tower of Babel, the original failed infrastructure project. Figure out how to do your APIs right if you use this opportunity at the conference to learn about route services, learn about how API management can work within Cloud Foundry. Every one of your teams can do APIs right, and you will be able to avoid this fate. Thank you.