Breaking the 2 Pizza Paradox with Platform Applications
summary
A team running 100–180 people supports tens of engagements with thousands of Git repos and tens of thousands of Jenkins jobs and builds a managed devops platform that each platform-instance team owns end‑to‑end. The platform uses CI/CD pipelines, semantic versioning and can be recreated from scratch (the team says it spins up tools and reference implementations in 10 minutes), supports Docker and Cloud Foundry patterns, encodes platform opinions and Phoenixes nightly, and successfully lowers adoption friction so business apps can deliver continuously.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:42What is DevOps
- 1:14DevOps definition
- 6:40What can we do
- 12:56Platform Engineering
- 17:23DevOps
- 19:33Sharing
- 22:54Takeaways
related talks
10mInterview
46mBeyond DevOps: How and Why Companies Converge on Platform Models
42mPlatform Engineering in practice — Why and How to start
05mHelp! My DevOps team is stuck!
31mPlatform Health: A team model of platform evolution
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations
47mPlatform Team Structures and Concerns
47mDevops, microservices and platforms, oh my!