Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Monday, May 11 • 1:30pm - 2:00pm
Next steps in the Cloud Foundry API and why 3 > 2

Sign up or log in to save this to your schedule and see who's attending!

The Cloud Foundry API is the interface for the platform's functionality, orchestrating a user's interactions with the system. In this presentation, core committers from the Runtime Team are going to explain the motivation, design, and architecture of the next iteration of the Cloud Foundry API. The team will discuss how the product goal to overhaul the concept of Apps in Cloud Foundry, paired with limitations from the existing V2 API, led to the design of a more flexible, consistent, and extensible API. Topics will include overcoming friction between new features within a well-established codebase, the goals and the driving ideas behind the V3 API and how they support new features and ease of future development, as well as a dive into the actual patterns and design of the API itself.

Speakers
JM

James Myers

Software Engineer, Pivotal
James Myers is a software engineer for Pivotal Software and a core contributor to the Cloud Foundry project. James is currently the anchor of the Diego team and has worked on Cloud Foundry for two years. He has presented previously at the 2015 and 2016 North American CF Summits.
ZR

Zach Robinson

Software Engineer, Pivotal
Zach Robinson is a Pivotal developer and core contributor to the Cloud Foundry platform. He is a member of the Runtime team, located in San Francisco, CA.
LS

Luan Santos

Software Engineer, Pivotal
Luan Santos is a Pivotal developer and core contributor to the Cloud Foundry platform. He is a member of the Diego team, located in San Francisco, CA. He also spoke at the CF Summit 2015 in Santa Clara, CA about the Cloud Foundry API.


Monday May 11, 2015 1:30pm - 2:00pm
Hall A-2

Attendees (133)