Better, Faster, Cheaper: What Does It Mean for Ops?
summary
Claims concrete wins: 2000x faster deployments and 100–200x better reliability by combining DevOps practices with containers. Uses Docker workflows, image scanning and signing, trusted registries, Compose-style service definitions, and LinuxKit immutable OS images so artifacts leave the desktop unchanged and carry bill-of-material metadata. Cites Toyota-style Andon feedback, Google-scale testing (100M tests/day), and cases—Aetna drops security defects from ~10 to zero—showing one service, one container, one port dramatically reduces risk and toil.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:55DevOps Training
- 1:28DevOps Poses
- 2:07What If
- 2:35DevOps Containers
- 4:06Faster
- 4:30DevOps
- 5:20DevOps Cookbook
- 6:40Culture
- 7:05The Science of DevOps
- 8:33The Iron Triangle
- 9:15Feedback Loop
- 9:53Not Cancel
- 11:06Google Test Cases
- 12:04Legendary Amazon Story
- 12:26Half a fielder
- 13:08DevOps is hard
- 14:37Hypervisors vs Containers
- 15:23Everything can be containerized
- 16:35Why Docker
- 20:38Pager
- 23:19Toyota Supply Chain
- 23:34Toyota Supply Chain Principles
- 23:56The Four Vs
- 25:48Docker
- 27:25Pannier
- 28:25Security Defects
- 29:46One Service
related talks
47mWhere the Security Rubber Meets the DevOps Road
27mDevOps Reality Check: Feels Faster or Really Faster?
34mDevOps: Next
24mHow DevOps changed the way we operate software
31mThe Data Behind DevOps: What Does It Take To...
45mDevOps: The Key to IT Performance
25mDevOps Handbook Experiments in Accelerating Delivery
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations