Modern Continuous Delivery
summary
Argues that continuous delivery must change for cloud‑first systems and gives concrete practices: store build artifacts as Docker images in a registry, deploy declaratively with Kubernetes and Helm, favor trunk-based development and use feature toggles to separate deploy from release, prefer canary or blue‑green over big‑bang releases, handle DB changes with expand/contract migrations, and automate environment provisioning so one automation can create many environments instead of repeatedly hand‑building them.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:42Some definitions
- 1:18Origins of Continuous Delivery
- 4:09Modern architectures
- 5:34Everything changes
- 6:43Build
- 9:50Test
- 13:50Security
- 14:44When should I modernize?
- 17:35Epilogue
related talks
30mModern Continuous Delivery
24mWhy, What, and How of Continuous Delivery
51mBetter software, faster: principles of Continuous Delivery and DevOps
26mWhere Are We Going? The Future of Continuous Delivery
40mContinuous Delivery Anti-Patterns
34mArchitecting for Continuous Delivery
32mContinuous Delivery Sounds Great But It Won’t Work Here
41mAll Things Continuous