Adrian Trenaman provides detailed examples of how HBC Digital has used Docker and what aspects of the technology haven't panned out as they thought they would.
Nicole Forsgren shares the results of studies spanning four years and 25,000 DevOps data points: continuous delivery and Lean management practices improves quality and security outcomes.
Philip Glebow discusses patterns, tools and processes used by Gap for integration, messaging, data, and scaling on Cloud Foundry, sharing lessons learned and plans for the future.
Andre Langevin and Mike Stolz discuss how Geode forms the core of many Wall Street derivative risk solutions which provide cross-product risk management at speeds suitable for automated hedging.
The authors discuss the top lessons learned from building a fully integrated developer platform, leveraging Cloud Foundry and OpenStack, answering questions from the audience.
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.
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.