Managing Feature Flags Efficiently
summary
A large React/Redux codebase (uploader says "3000K lines") adopts a concrete pattern: pull flag evaluations into flags in Redux store, expose a toggler HOC at unit boundaries (components/reducers/actions), keep old and new versions in separate files, and automate add/remove with a shell script to remove flags. The result is measurable: rollouts (example 5%) and rapid rollbacks work, developer velocity returns, at the cost of short-lived duplicated code.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:25A feature flag is a conditional
- 8:59Control release
- 9:30Example use
- 14:08Digression: Structured programming
- 17:15File system structure
- 18:12Example toggler creation
- 19:45Old component
- 19:55New component
- 21:09Removal Process
related talks
30mFeature Driven Architecture
25mReleasing apps faster with feature flags
07mSetting Up Feature Flags with React
44mFlags of Flexibility - Unlocking Rapid Iteration
50mFunctional Feature Flags
26mMove Fast and (Don't) Break Things
33mUnlock the Power of Feature Based JS Development
41mFeature Flags: Separate Deployment from Feature Release