Architecture 2
OpenFeature can reduce vendor coupling, but “we use OpenFeature” does not mean one feature platform can be replaced by another with no migration work.
What becomes more portable
When applications use common evaluation capabilities, the code can remain relatively stable:
getBooleanValue(...)
getStringValue(...)
getNumberValue(...)
getObjectValue(...)
+ evaluation contextA provider translates that standard API to the selected platform.
What remains vendor specific
- flag definitions and dashboard organization
- complex targeting syntax
- segments and audience management
- approval workflows
- experimentation statistics
- release guardrails
- observability correlation
- audit and lifecycle tooling
These features live in the control plane rather than in the basic evaluation call.
Portability is a spectrum
| Usage | Portability |
|---|---|
| Boolean evaluation with simple context | high |
| typed configuration | generally good if provider supports it |
| vendor specific segments and workflows | moderate to low |
| proprietary experiments and guardrails | low at control plane level |
Do not build your own abstraction on top of the abstraction without a reason
Some enterprises respond to vendor lock in by creating a large internal feature flag API that hides every platform capability. That can produce a lowest common denominator and make the internal wrapper itself a permanent platform to maintain.
Prefer the standard API where it fits. Add enterprise conventions around context, initialization, testing and governance rather than rewriting the whole feature management ecosystem.
Migration should be tested before it is needed
If portability is an architectural requirement, prove it with one representative application. Configure two providers in a nonproduction environment and measure what actually changes. This reveals which dependencies are in code and which are in control plane configuration.
OpenFeature is most valuable when it is treated as a deliberate application contract, not as a marketing checkbox that promises zero switching cost.
Feature Flags series
← Designing an Enterprise Feature Management Architecture Feature Flags, Progressive Delivery, and Observability →