DevOps Patterns and Antipatterns for Continuous Software Updates
summary
Concrete failure stories and concrete remedies: Java switches to six‑month releases since 2017 and the State of DevOps finds ~20% “elite” teams deploying multiple times per day; examples include Google Wi‑Fi updates resetting devices to factory settings, Jaguar I‑PACE recalls for brake software, Tesla’s phantom braking fix delayed by batch releases, CloudFlare outage from a misconfigured rule, and MoviePass going offline for weeks. Coverage shows local rollback, canary/progressive releases, feature flags, observability and automated frequent deploys, with advice on when each actually works.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:30Why We Even Bother To Update Software
- 3:47Security Vulnerabilities
- 8:36Java
- 13:59Implement Local Rollback for the Devices
- 22:32Observability
related talks
50mDevOps Patterns & Antipatterns for Continuous Software Updates
30mDevOps Patterns and Antipatterns for Continuous Software Updates
48mDevOps 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
51mBetter software, faster: principles of Continuous Delivery and DevOps