DevOps Patterns and Antipatterns for Continuous Software Updates
summary
Examines concrete incidents and data about update practices—e.g., many teams still run old Java or legacy Windows—then argues for DevOps patterns that enable safe continuous updates: canary releases, local rollback, automated progressive delivery with good monitoring, and staged over-the-air (OTA) rollouts for cars. Contrasts those effective patterns with failures from ad-hoc, manual, or big‑bang updates illustrated by real outages and losses (Knight Capital, Cloudflare regex outage, NHS ransomware, Nuvi).
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:07Why update software
- 3:49Evolution of updates
- 4:51Security drives updates
- 7:19DevOps and fast updates
- 13:01DevOps Report role
- 15:10Frequent update methods
- 16:33Java update trust issues
- 21:15Testing and staging death
- 23:41Risks slow updates
- 26:49Restoring update trust
- 27:11Google Wi-Fi success
- 28:57Failed update: rollback
- 30:21Monitor driver rollback
- 31:05Car software update problems
- 32:52Tesla phantom braking
- 35:42Cloud vs car updates
- 36:46Knight Capital error
- 40:22Clubhouse regex failure
- 41:54Canary releases
- 43:00MoviePass failure
- 44:05Summary
- 45:33Updating planes mid-flight
related talks
30mDevOps Patterns and Antipatterns for Continuous Software Updates
50mDevOps Patterns & Antipatterns for Continuous Software Updates
27mDevOps Patterns and Antipatterns for Continuous Software Updates
17mDevOps Patterns & Antipatterns for Continuous Updates
42mPatterns and Antipatterns of Continuous Deployments in DevOps Practice
05mDo this, not that: Antipatterns in Continuous Deployment
46mContinuous delivery antipatterns
18mDesign Patterns For Efficient DevOps Processes