Bridging the Gap CICD Mind the Gap
summary
Argues that automation, small batches and SRE practices let teams push changes in days not months, citing banks doing thousands of deploys and recommending feature flags plus blue-green deploys or canary at 5–10% to reduce risk. Recommends infrastructure as code, CI pipelines (GitHub Actions, actuator-style hooks), monitoring/tracing and PagerDuty-style alerts, uses an error budget (99% uptime) to align teams, and warns with Knight Capital and $100k cloud-bill stories about unsafe manual change.
AI-written summary · about
chapters (6)
- 0:00Start
- 15:33Error Budget
- 17:25What Can We Do To Get More Features to Production More Frequently
- 25:47Trust in the Process
- 28:28Deployment Strategy
- 35:15How Long Should We Live in the Canary Stage
related talks
59mBridging the Gap Between Ops and Developers with CI/CD
55mBridging the Gap Between Ops and Developers with CI/CD
51mBetter software, faster: principles of Continuous Delivery and DevOps
41mEnable your team to do changes in production
40mContinuous Delivery Anti-Patterns
17mCI/CD - Build/Deploy Automation
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
01h 02mTools and Techniques for Infrastructure as Code