Feature flags: the toggle, the A/B test and the canary
summary
Demos show concrete patterns: MVC samples use FeatureToggle (C#) for strongly typed on/off and date-based toggles, Azure App Configuration + feature management for a centrally polled flag (~30s) that instantly reveals a hidden controller, and LaunchDarkly for user segments, percentage rollouts and syncing between test and prod. FeatureToggle lacks telemetry and looks unmaintained; LaunchDarkly handles targeting and metrics. Canary releases use targeted segments and metrics to roll out safely. Advice: remove stale flags, avoid daisy chaining, and don’t build your own flag service.
AI-written summary · about
chapters (6)
- 0:00Introduction to feature flags
- 3:12Anatomy of a feature flag
- 8:51Deployment vs. release
- 15:37Frameworks and services
- 27:32Implementation and demos
- 53:39Canary releases and best practices
related talks
41mFeature Flags: Separate Deployment from Feature Release
20mFeature Flag-Driven Development… in Reverse
44mFlagging features — a DevOps approach to continuous release
11mFeature flag use cases you haven't heard about yet
35mFeature Toggles: The Good, The Bad, and The Ugly
54mFeature Flags Separate Deployment from Feature Release
08mThe Art of Feature Flagging
59mFaster & less risky releases with feature flags