100 releases per day
summary
Describes achieving continuous deployment at very high frequency — aiming for around 100 releases per day — by using techniques like feature flags, automated CI/CD pipelines, and careful rollback/monitoring strategies. Covers practical engineering practices and tooling to manage risks of frequent releases and keep services stable under rapid deployment.
AI-written summary · about
chapters (17)
- 0:00Start
- 5:08Branching model: 2012-2015
- 5:57Deployment: 2012-2015
- 6:19Branching model: 2016-2018
- 7:34Deployment: 2016-2018
- 9:25Branching model: 2018-2019
- 10:25Deployment: 2019: staging
- 11:57Deployment: 2019: skaffold
- 14:56Deployment: Prod
- 15:47Enablers: Feature switchers
- 18:39Enablers: quick code reviews
- 24:13Enablers: Quality gates: schema
- 24:56Tooling: Monitoring: DD+Prometeus+Graf
- 27:03Tooling: Jenkins JJB
- 28:22Tooling: Exception management: Sentry
- 29:08Enablers: Culture
- 35:11Challenges
related talks
44mRelease Early, Often, Stable
05mRelease management as a catalyst for CI/CD
44mI Deploy On Fridays
41mFrequent Releases & Major Changes
33mContinuous Delivery - What does good really look like?
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
28mMinimum Viable Continuous Delivery
47mI Deploy on Fridays (And Maybe You Should Too)