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.
Michael Hausenblas introduces containers, microservices and dealing with security, monitoring and troubleshooting using Apache Mesos/Marathon and Kubernetes.
Rachel Reese talks about the lessons she has learned at Jet.com on their way to developing the platform and how they’ve schooled themselves on what works and what doesn't for F# and microservices.
Tushar Dadlani focuses on lessons learned while building the continuous integration pipeline for deploying Pivotal Cloud Foundry to production.
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.
Christopher Grant and Eric Johnson talk about Home Depot's experience in piloting Spring apps running in Pivotal Cloud Foundry on top of Google Cloud Platform.
David Xia explains how Helios testing framework drives integration tests and spins up self-contained environments during test runs, increasing Spotify’s code quality and successful deployments.
Luke Kosewski describes Flow, how it adds value to a microservice architecture, what preconditions must be met for such a recovery mechanism to succeed, and tells the story of a 2015 Q4 outage.