Immutable Awesomeness?
summary
Argues that pairing containers with software supply‑chain practices reduces unplanned work by improving traceability and hygiene: shows apps average 106 components with 23% vulnerable and 8% restrictive licenses, quantifies fixes as ~2 components per incident at ~$2k each, scales to $6M and 60,000 hours for 2,500 apps, cites tooling wins (Docker images, Jenkins Docker build slaves, Postgres test snapshots), cites performance examples (IBM: 150 Apache servers in 36s; Google: 2.2B containers/week).
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:40Security vs DevOps
- 11:40Software is eating world
- 16:40Whoops
- 20:00John Willis
- 21:04Martin Fowler
- 21:57Why order matters
- 24:49Immutable infrastructure
- 26:06The 4th V
- 27:02Lean Startup Model
- 30:10Variation
- 31:20Case Study Guilt
related talks
06mRethinking the Software Supply Chain: Trust, Minimalism, and Resili...
40mPanel Discussion: Open Source Supply Chain Security - Are Containers..
45mPanel Discussion: Managing Open Source...
38mSo. Many. Vulnerabilities. Why are containers such a mess...
32mAdapting DevOps in a World of Growing Software Supply Chain Attacks
37mThe Death Star and the Ultimate Vulnerability
29mFragile by Design: Large-Scale Evidence of Supply Chain Risk
34mWhat We Learned Dissecting the World's Most Popular Containers
