Alan Ho and Sandeep Murusupalli discuss the right type of protection (OAuth/Throttling) and monitoring (e.g. bot monitoring) needed to be put in place to properly manage microservices.
Tom Collings, Dustin Ruehle talk about the benefits of generating a tile in CF, the criteria used to decide whether a tile is best for an organization, demoing tile generation and maintenance.
The authors discuss the top lessons learned from building a fully integrated developer platform, leveraging Cloud Foundry and OpenStack, answering questions from the audience.
Paul Warren explains how the CF runtime was extended to include persistent storage, demonstrating scaling an application that accesses data on a NFS volume and discussing the future of persistence.
Jay Marshall and Vic Iglesias talk about how GCP was built for the enterprise, enabling users to deploy their applications on the same infrastructure Google uses for search, YouTube or GMail.
Tushar Dadlani focuses on lessons learned while building the continuous integration pipeline for deploying Pivotal Cloud Foundry to production.
Rossen Stoyanchev reviews the main features in Spring Framework 4.x and previews the work towards Spring Framework 5.
John Northrup demonstrates how GitLab helps developers along their entire workflow from first commit, issue tracking, continuous integrations, and deployment into Pivotal Cloud Foundry.
Colin Humphreys talks about how the Cloud Foundry community deploys the distributed system powering the one of the most successful open source platforms, along with details on the tooling used.
Casey West uses twelve-factor app essay as a guide to discuss the do’s and dont’s of building and running containers, each factor providing an opportunity to consider avoiding certain anti-patterns.
Amit Gupta talks about how Cloud Foundry does continuous integration, from a GitHub pull request against a small repository to an official final release, transparently working with the community.
Anthony McCulley describes The Home Depot’s first year with Cloud Foundry, adopting the platform, scaling to hundreds of developers across multiple data centers, and mistakes made along the way.