Patterns and Antipatterns of Continuous Deployments in DevOps Practice
summary
Examines real-world failures during continuous software updates across environments from Kubernetes microservices to desktop JavaScript apps and even cars, identifying what went wrong. Reviews concrete DevOps patterns and antipatterns and shows how applying the right practices (not manual end-to-end human checks) could prevent these update disasters, offering actionable ideas attendees can apply immediately.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:08Why update software
- 7:12Security and updates
- 13:40Baruch Sadogursky
- 15:31Why not update yet
- 22:21Update trust issues
- 29:48Updates in cars and devices
- 33:20Continuous Deployment vs Delivery
- 37:16Progressive delivery and rollbacks
- 38:20Updates in aviation and critical systems
- 40:32Summary and Q&A
related talks
48mDevOps Patterns and Antipatterns for Continuous Software Updates
27mDevOps Patterns and Antipatterns for Continuous Software Updates
17mDevOps Patterns & Antipatterns for Continuous Updates
50mDevOps Patterns & Antipatterns for Continuous Software Updates
30mDevOps Patterns and Antipatterns for Continuous Software Updates
33mThe DevOps disaster: 15 ways to fail at DevOps
46mContinuous delivery antipatterns
05mDo this, not that: Antipatterns in Continuous Deployment
