Patterns & Playbooks to Make Every Commit Production Ready
summary
Claims practical steps to make every commit deployable with zero downtime by breaking changes into additive steps, using blue/green or canary rollouts, and testing compatibility rather than relying on DB rollbacks. Shows a real fintech running 100+ engineers on master and deploying every two weeks, contrasts a failed four‑day migration that lost a client, and demos a five‑step rename (first+last → full name). Recommends scientist library, Flyway/Liquibase, branch by abstraction, schema backwards compatibility test.
AI-written summary · about
chapters (11)
- 0:00Introduction and personal story
- 3:28Revolutionary fintech deployments
- 8:27Blue-green deployment risks
- 13:04Adding new features safely
- 20:44Refactoring live code
- 29:08Evolving APIs and contracts
- 30:53Database schema migrations
- 42:49Potential pitfalls and lessons
- 47:24Beyond the basics
- 48:27Where to start and next steps
- 50:10Q&A
related talks
46mContinuous delivery antipatterns
36mUnlocking the Benefits of Database DevOps and Automation
40mStrategies for Zero Down Time, Frequent Deployments
45mEnabling Continuous Delivery with Database Practices
23mContinuous Deployment - The Last Frontier for Continuous Delivery
34mGuide to Continuous Deployment with Rails
20mLessons Learned from Building a Deployment Process for 100+ Devs at a Large Bank
41mContinuous delivery in 10 easy mistakes