Strategies for Zero Down Time, Frequent Deployments
summary
Claims a practical path to near zero downtime with concrete patterns: blue/green deployments and rolling updates, Kubernetes/Elastic Beanstalk/Heroku support, Docker artifact builds, and automatic rollbacks. Covers db gotchas like Postgres locking and using concurrent indexes, a three-step migration for backwards compatibility, feature toggles, canary API tests and shadow traffic, separate worker tiers for Celery, and an anecdote where a maintenance-window rollout stretches six weeks versus an estimated three.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:33What Is Downtime and Why Do We Normally Have Down Time
- 1:56Maintenance Windows
- 4:41The Deployment Death Trap
- 5:40Continuous Delivery
- 7:00More Secure Code
- 9:45How Exactly Does One Have no Downtime
- 13:03Common Deployment Strategy
- 16:23Backwards Compatibility
- 16:58Applications Need To Be Stateless
- 19:19Versions
- 21:23Concurrent Indexes
- 22:46Data Migration
- 23:13Always Run Your Migration before You Deploy
- 23:38Catch Migration Failures
- 23:58Three-Step Deploy Process
- 27:33Rollbacks
- 28:32Canaries
- 29:59Shadow Deploys
- 32:01How a Feature Toggle Works
- 33:38Worker Tier
- 37:03Schema Migrations
related talks
37mZero-downtime Deployment Strategies (...) [ENG]
35mZero-Downtime Deployment on Kubernetes
34mDeploying Without Crying: Deployment Strategies for Peaceful Nights
29mParticular Particulars about "Zero Downtime Deploys"
01h 04mZero Downtime Application Deployments on Azure PaaS
32mZero Downtime Deploys Made Easy
37mZero downtime Deployment on Kubernetes
50mZero Downtime Migrations with Spring Boot