Type-safe Feature Flagging in OpenFeature: Lessons Learned From Using Feature Flags at Google
Talkat KubeCon + CloudNativeCon Europe 2025 · on Friday, 2025-04-04· at 11:45· Level 1 | Hall Entrance N10 | Room H·
summary
Google reports ~150k feature flags and ~70% developer usage and adopts a policy that flags must exist in the flag system before appearing in code; reflective access is disallowed and stale references break compilation. The project builds a vendor-agnostic CLI that fetches a local manifest and generates language bindings (React hooks demo works), producing type-safe accessors that prevent typos and default-mismatch outages and integrates with multiple providers as OpenFeature CLI generated clients.
AI-written summary · about
chapters (9)
- 0:00Introduction to speaker
- 1:30Understanding feature flags
- 2:39Feature flags at Google
- 5:58Operational challenges
- 11:56Google's codegen approach
- 13:55OpenFeature overview
- 16:33OpenFeature CLI introduction
- 19:23Live demonstration
- 22:33Community and conclusion
related talks
38mFun with Flags: How OpenFeature Solves Your Feature Flag Headaches
43mFeature Flags with OpenFeature: Faster, More Collaborative Development
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
50mThe Story of One Feature Flag
43mOpenFeature -- one flag to rule them all
05mFeature Flags
05m5 Life Hacks Using Feature Management
59mMastering Feature Flags: Best Practices with Firebase Remote Config