Fun with Flags: How OpenFeature Solves Your Feature Flag Headaches
summary
A vendor-agnostic API called OpenFeature provides language SDKs and four concrete tools: the evaluation API, pluggable providers, an evaluation context for deterministic rollouts, and hooks (including an OpenTelemetry hook) that emit metrics to find stale flags. The presentation cites Knight Capital’s half‑billion dollar one‑hour loss as why safe rollouts matter, shows flagd and Flexmith as working reference implementations, and reports large orgs (Booking.com, Dynatrace, Google) using OpenFeature in production to avoid vendor lock‑in and surface obsolete flags.
AI-written summary · about
chapters (10)
- 0:00Introduction and feature flag disasters
- 2:14What are feature flags
- 7:55What is OpenFeature
- 14:19Avoiding vendor lock-in
- 16:06Dynamic evaluation and targeting
- 22:49Managing obsolete feature flags
- 24:14Hooks and observability
- 26:43Key OpenFeature concepts
- 28:28OpenFeature community and adoption
- 30:14Q&A session
related talks
43mFeature Flags with OpenFeature: Faster, More Collaborative Development
25mType-safe Feature Flagging in OpenFeature: Lessons Learned From Using Feature Flags at Google
32mOpenFeature Update From the Maintainers
45mBye Bye Vendor Lock-in: Standardize Your Feature Flags with OpenFeature
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
43mOpenFeature -- one flag to rule them all
50mThe Story of One Feature Flag
05mFeature Flags