Feature Flags Separate Deployment from Feature Release
summary
Shows a working Node/React demo that moves feature flags from config-file + env vars to a database with per-user overrides and to a SaaS provider, using the LaunchDarkly SDK. Demonstrations include client-side loading and sensible defaults, CDN/static JSON caching versus runtime API calls, tests that fail builds on expired flags, and the practical problem of stale caches and rollout inconsistency across servers. Code runs live during the talk with minor demo hiccups but the patterns and tradeoffs are concrete and reproducible.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 9:45What are feature flags
- 13:55Anti-patterns solved by flags
- 23:03Best practices and context
- 24:07Demo: Config file implementation
- 35:27Demo: Client-side flags
- 37:11Demo: Database storage
- 45:23Demo: Context overrides
- 48:38Demo: External service
- 51:36Summary and use cases
related talks
41mFeature Flags: Separate Deployment from Feature Release
02mA Message From LaunchDarkly
50mThe Story of One Feature Flag
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
01h 09mFeature flags: the toggle, the A/B test and the canary
24mSkip the Deployment Queue: Automated Rollouts and Rollbacks Using OpenFeature
35mA Deployment Is Not a Release, Controlled Launches with Feature Flags
44mFlagging features — a DevOps approach to continuous release