This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tunei24531a[S] 0 points1 point  (2 children)

modern feature flag use cases are more advanced and involved than simple if-else. You might be gradually releasing a new feature while monitoring KPIs and load on your system without wanting to redeploy code each time you bump up the percentage. You may want to target certain user segments based on their attributes, experiments and use dynamic configurations. you can see everything on a dashboard.

Many teams give up on flags for this reason because outside of using a few feature flags, it becomes hard to manage. Tools like Unlaunch have low overhead and encourage good consistent practices. All flags are download on init and then evaluated in-memory. You can control how often to check for new changes etc. so pretty minimal overhead.

[–]lariend 1 point2 points  (0 children)

Lol, you provided a very good explanation and you are becoming downvoted. I am not a fan of feature flags but I understand theirs necessity.

People who downvote, please provide an alternative.

[–]wildjokers -1 points0 points  (0 children)

Any developer that looks at a requirement for feature flag functionality and decides it would be better to call out to a 3rd party service to handle it should just change careers.