Flagging features — a DevOps approach to continuous release
summary
Claims that feature flags let teams deploy first, release later and turn a kill switch on instantly, implemented with Azure App Configuration + .NET Feature Management or commercial products like LaunchDarkly/Unleash. Practices include rings and A/B testing, telemetry-driven quality gates, and dark launches; examples: canary audiences of tens, early adopters in the thousands, GA in the millions. The concrete build is an externalized feature service, integrated with pipelines and monitoring, and it yields automated, observable rollouts when flags and cleanup are enforced.
AI-written summary · about
chapters (8)
- 0:00Start
- 12:58Feature management Rules and settings for evaluation in feature toggle
- 15:29Ingredients for feature management In process service for evaluation
- 16:25Tools and platforms for feature management Software as a Service
- 19:27Telemetry Essential to monitor your solution when toggling
- 21:34Development cycle with feature flags
- 28:09Test strategies
- 30:59Dealing with technical debt Lifecycle of flag
related talks
41mFeature Flags: Separate Deployment from Feature Release
59mFaster & less risky releases with feature flags
08mThe Art of Feature Flagging
35mA Deployment Is Not a Release, Controlled Launches with Feature Flags
01h 09mFeature flags: the toggle, the A/B test and the canary
43mBuilding a .NET Core App with Microsoft.FeatureManagement
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
14mReducing Release Risk with Feature Flag Management