You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenFeature (https://openfeature.dev/) strives to provide an independent standard for working with feature flags.
A standard access library is called a 'provider' in OpenFeature ecosystem. There are several providers for many vendors already provided there: https://openfeature.dev/ecosystem.
Having FeatureHub provider would greatly ease the integration.
Describe alternatives you've considered
Alternative solution to use directly FeatureHub's SDK is basically a vendor lock-in and my organization is more likely to adopt OpenFeature supported provider.
This seems promising in terms of not needing to maintain separate SDKs for OpenFeature, but instead expose a compatible API.
Actually, I played with this a little and I think we would lose the well designed fallback (cached local eval) and update mechanisms (SSE) if we used the ofrep. So IMO language specific wrappers of the FeatureHub SDKs for OpenFeature would be the path to go.
OpenFeature (https://openfeature.dev/) strives to provide an independent standard for working with feature flags.
A standard access library is called a 'provider' in OpenFeature ecosystem. There are several providers for many vendors already provided there: https://openfeature.dev/ecosystem.
Having FeatureHub provider would greatly ease the integration.
Describe alternatives you've considered
Alternative solution to use directly FeatureHub's SDK is basically a vendor lock-in and my organization is more likely to adopt OpenFeature supported provider.
https://openfeature.dev/
https://openfeature.dev/ecosystem
The text was updated successfully, but these errors were encountered: