DevOps Patterns & Antipatterns for Continuous Software Updates
summary
Talk catalogs concrete failure cases and practical fixes: frequent six‑month Java releases see 83% of surveyed devs still on Java 8 because verification cost blocks upgrades; Spectre-like hardware bugs make fast patching critical; Night Capital Group loses about $114M from a partial rollout that reused APIs; Cloudflare goes down after a bad regex spikes CPU; Google Wi‑Fi auto‑update factory‑resets users. Recommended patterns are canary releases, observability and tracing, feature flags for fast rollbacks and, where feasible, local rollback and zero‑downtime automated deployments.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:14Why We Want To Update Software
- 11:12Cultural Map
- 28:02Phantom Breaking
- 37:30Knife Capital Group
related talks
30mDevOps Patterns and Antipatterns for Continuous Software Updates
27mDevOps Patterns and Antipatterns for Continuous Software Updates
17mDevOps Patterns & Antipatterns for Continuous Updates
48mDevOps Patterns and Antipatterns for Continuous Software Updates
42mPatterns and Antipatterns of Continuous Deployments in DevOps Practice
05mDo this, not that: Antipatterns in Continuous Deployment
46mContinuous delivery antipatterns
35mThe Dawn of Liquid Software