Contain yourselves
summary
Argues that containers (Docker, LXC) solve packaging not operations, and warns they break reproducibility and obscurify what’s running; cites concrete tooling tradeoffs: Puppet/Chef/Ansible for config, Kubernetes for orchestration, Apache/MySQL in production. Gives numbers and practices: Booking grows ~60% year‑over‑year, runs 8 rollouts a day, does weekly production capacity tests by stressing a “cell,” and budgets for human failure. Claims containers work well for isolated builds and multi‑tenant hosting but containers are packaging not ops panacea.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:54Myth of good old days
- 4:45Web-native disruptors
- 6:49Speed and agility
- 8:54Dev to prod without friction
- 11:59Automating infra and config
- 14:47Infra as code benefits
- 15:30Testing in production
- 17:57Rise of DevOps
- 21:04Contrasting incentives between development and operations
- 23:09Containers and Docker hype
- 27:20Why Docker fails in enterprise
- 30:07Docker reproducibility problem
- 31:50Legitimate container uses
- 33:56Banks adopting DevOps
- 35:23Microservices and Kubernetes myths
- 38:11Hidden costs of orchestration
- 38:53Scaling to 100K machines
- 40:37Business vs container infra
- 41:20Satire of modern systems
- 42:02Booking.com eight rollouts
- 42:43Closing remarks
related talks
56mDevOps in a containerized world
47mContinuous Delivery with Containers: The Good, Bad, & Ugly
38mIt's a Trap! How Abstractions Have Failed Us.
32mWhy you´re not ready for Containers in Production!
42mCloud Native Applications
46mDeploying and maintaining software for today's infrastructure
52mOperating Container-Based Infrastructures
59mBeyond Docker Buzzwords