Bye Bye Vendor Lock-in: Standardize Your Feature Flags with OpenFeature
summary
Introduces OpenFeature, a CNCF-incubating standard that unifies Feature Flag APIs to avoid vendor lock-in. Covers what feature flags are, why a standard was needed, OpenFeature’s architecture and API unification, and shows how to switch feature-flag backends by changing three configuration lines without touching business code.
AI-written summary · about
chapters (12)
- 0:00OpenFeature intro
- 1:48What are feature flags
- 8:19Vendor lock-in problems
- 10:25OpenFeature standard
- 12:30OpenFeature providers
- 15:37Demo: Go & JS
- 23:20Switch providers easily
- 24:02Extensions & ecosystem
- 28:15Better dev experience
- 30:41Adopting OpenFeature
- 32:28CNCF adoption
- 33:50Q&A
related talks
38mFun with Flags: How OpenFeature Solves Your Feature Flag Headaches
31mTurn Me On With Cloud-Native Feature Flags!
43mOpenFeature -- one flag to rule them all
44mFlagging features — a DevOps approach to continuous release
27mLevel Up Your CI/CD With Smart AWS Feature Flags
30mDesigning a modern Feature Flags Controller
40mTightrope Walking: Best Practices & Lessons Learned on Community and Business Buildi...
22mOpen Standards: Anchoring Extensibility for Cloud-Native Tooling
