Master your software delivery with feature flags
summary
Explains how feature flags cut risky releases into controlled steps by treating toggles as code, wiring them into CI/CD and monitoring, and rolling changes to small cohorts then ramping up. Shows canary rollout patterns with real percentages 5% to 50%, describes using automated toggles plus health metrics to detect regressions and roll back instantly, and cites an incident timeline where minutes of downtime and long rollback delays motivate this approach.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:27What is software delivery
- 4:33Why automation matters
- 12:13Feature flags explained
- 18:20Benefits of feature flags
- 22:21Monitoring feature flags
- 27:27Real-world example
- 30:20Conclusion and thanks
related talks
59mFaster & less risky releases with feature flags
05m5 Life Hacks Using Feature Management
35mFeature Toggles, Trunk-Based Development and Continuous Delivery
50mThe Story of One Feature Flag
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
28mHow We Progressively Deliver Changes To Kubernetes Using Canary Deployments and Feature Flags
08m⚡ Lightning Talk: The Hidden Costs of Feature Flags: Understanding and Managing Adoption Challenges
15mFeature Flags