What's the major differences between flagd vs go-feature-flag #740
-
|
There is a default implementation in Openfeature org so call |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
|
FlagD and GO Feature Flag are two open-source solutions designed to help developers experiment with feature flagging in a simple way. Both solutions share the common goal of providing a way to control feature flags and experiment with new features, with the aim of minimizing the risk of bugs and other issues. However, while they have a lot in common, there are also some differences between the two solutions. FlagD is a feature flagging solution specifically designed for use in Kubernetes. It is built to work seamlessly with Kubernetes and its associated technologies. Therefore, if you are using Kubernetes, FlagD may be a better fit for you as it has been created with this ecosystem in mind. GO Feature Flag, on the other hand, is a more versatile solution that can work with a wide range of configuration locations outside of Kubernetes, such as AWS S3, Google Cloud, GitHub, Gitlab, etc... It can also work with configmaps inside Kubernetes. Moreover, GO Feature Flag has more advanced rollout capabilities with the support of experimentation, progressive delivery, schedule changes, etc... This means that you can use GO Feature Flag to experiment with new features and roll them out to users gradually, helping to minimize the risk of bugs and other issues. In summary, FlagD is more focused on the Kubernetes ecosystem, while GO Feature Flag is a more versatile and feature-rich solution that can be used in a wider range of environments. @yangzhaox I hope it gives you the information you were looking for? |
Beta Was this translation helpful? Give feedback.
-
|
Oh this looks great. I was thinking how to do this in json format. About jsonlogic, the possible advantage is if one day you want to evaluate the targeting rule in frontend, it has javascript implementation. |
Beta Was this translation helpful? Give feedback.
-
|
Given the above use case, how to use GOFF editor to do that? I feel a single-line input for query is not an easy way to define such a multiple-line rule. And YAML format is better at readability than JSON in this case. |
Beta Was this translation helpful? Give feedback.
-
|
I have an idea to enhance GOFF editor: in fact it can be turned into a GOFF playground where not only a rule can be defined but also it can be tested with manually entered user context data without attaching to GOFF relay proxy. The key to enable this is the rule can be evaluated purely in JS on the frontend. What do you think? |
Beta Was this translation helpful? Give feedback.
-
|
@yangzhaox sorry for the late reply be this is actually a lot of good things here. Since this is not my biggest expertise I haven't spend that much time on it, and I would love to have contributors to help me with it. If by any chance you know someone that can help with that, it would be awesome 👍 |
Beta Was this translation helpful? Give feedback.
-
|
@yangzhaox can I ask you to create some issues with your ideas? |
Beta Was this translation helpful? Give feedback.
FlagD and GO Feature Flag are two open-source solutions designed to help developers experiment with feature flagging in a simple way. Both solutions share the common goal of providing a way to control feature flags and experiment with new features, with the aim of minimizing the risk of bugs and other issues. However, while they have a lot in common, there are also some differences between the two solutions.
The main difference between FlagD and GO Feature Flag is their ecosystem and versatility.
FlagD is a feature flagging solution specifically designed for use in Kubernetes. It is built to work seamlessly with Kubernetes and its associated technologies. Therefore, if you are using Kuber…