spec VS Togglz

Less Vendor Lock-in: Open source means less vendor lock-in by nature. Many open source feature flag solutions are also partnered with OpenFeature to promote open standards, community, and less lock-in at the code level.

Instead of returning a static value, the code above uses OpenFeature and the Flagd provider (feature flag backend) to retrieve flag values (we will see how flagd reads the JSON file soon). If the feature flag system is offline or unavailable for whatever reason, a safe fallback value of #FFFFFF is returned.

Open-source & standardise interfaces - DevCycle tries to make every piece of software that their clients install open source. With CNCF, they are leading a project called OpenFeature - a vendor-agnostic interface for feature flagging.

The trend in feature flag implementation is to standardize with solutions like OpenFeature that provide SDKs and templates to streamline the process. Standardization is beneficial for 2 reasons:

For those that dont know about the project, check out Open Feature https://openfeature.dev/ which is sort of like Open Telemetry but for feature flags. Helps avoid vendor lock in. We're a young project and looking for help and to build the community!

What is the OpenFeature Standard?

Shameless plug here for openfeature - a CNCF standard for managing and implementing feature flags: https://openfeature.dev/

Added Togglz support. Togglz is a really cool library we love and use. We have added an admin console to the app.

While it's fairly easy to implement all the logic of feature toggles manually, I recommend that you use a library for this purpose. Some options are: togglez (Java), fflip (JavaScript), NFeature (.NET), among many others.

What about something simpler, like https://www.togglz.org/ ? Handy if you need it for single service.