Build Progressive Delivery and Safety Into Your Apps with Feature Flags
summary
Claim: embed vendor-neutral feature flags and observability into the app to do safe progressive delivery and runtime fixes. Uses OpenFeature as the API layer, OpenTelemetry + Jaeger for traces, and flagd as a flag backend; toggling a demo flag changes span time from ~74 µs to 2 s (the demo flag slowly_roll=true). Targeting uses JSON logic (user-agent rule for "GPT bot"), swapping backends only changes three provider lines, and multiple providers (six or seven) commonly coexist.
AI-written summary · about
chapters (8)
- 0:00Progressive delivery intro
- 1:06Delivery strategies
- 5:41Tooling vs feature flags
- 8:15Flagger for canary
- 10:21Feature flag safety cases
- 13:12Decoupling with OpenFeature
- 17:16Live demo: flagged dice
- 24:46Summary & future-proofing
related talks
38mFun with Flags: How OpenFeature Solves Your Feature Flag Headaches
39mFun with Flags: How OpenFeature Solves Your Feature Flag Heada...
43mFeature Flags with OpenFeature: Faster, More Collaborative Development
25mType-safe Feature Flagging in OpenFeature: Lessons Learned From Using Feature Flags at Google
05mFeature Flags
50mThe Story of One Feature Flag
43mOpenFeature -- one flag to rule them all
59mFaster & less risky releases with feature flags