I'm currently evaluating tools to add feature flags to my application at work. Looking for open-source or SaaS tools you folks have used or are currently using.
Hi, I'm a Developer Advocate at LaunchDarkly: <a href="https://launchdarkly.com/" rel="nofollow">https://launchdarkly.com/</a><p>Obviously I'd like you to use our service, but I'd rather that you find the one that best suits your business needs. There are plenty of good open source feature management systems out there. Just - whatever you do - don't fool yourself into building your own. Your time's worth more than that.<p>If you want a deeper argument, I wrote it up here, along with some examples of good open source systems: <a href="https://launchdarkly.com/blog/feature-management-platform-build-or-buy/" rel="nofollow">https://launchdarkly.com/blog/feature-management-platform-bu...</a>
I think something to note on this as I already see this in the comments. There's always the suggestion of "Yeah that's easy we could do that".<p>To this I'd say it totally depends on the usecase, I've seen 10s of tech teams build this badly and end up causing more harm than good, some even just static config files that require a build to change which totally defeats the point.<p>I think looking for an open source tool is great, to this I'd say consider the following :<p>- Before anything else, you'd definitely want the ability to turn the flags off per environment (dev/prod etc) without having to deploy code.<p>- Do you want to control who can manage features? Quite often you'd want to enable non-tech people to manage / test features.<p>- How scalable does it need to be? Some people might want to just not have to worry about serving thousands or millions of flags.<p>- Do you want to serve flags based on users or maybe even groups of users? I've seen attempts at this but then you start having to worry about setting traits and building some sort of rules engine.
I've worked with Split.io at a client, they had libraries for our frontend and our backends. Their interface was also neat and would allow you to separate out your feature flags per environment, per user or user group, or through any other custom condition. They'd also provide statistics for A/B testing, but I never got that far with them to try it out.<p>Theirs was dynamic in that you could change the rules and at a given interval the connected user's app would refresh and react accordingly. It was pretty complex, I suppose, but I'd roll out my own and go to something like them if I had a lot more conditions or targets.
If you mean global feature flags, use the config file built into virtually every single webframework and and an if statement.<p>It's really not complicated.<p>Some webframeworks require an app restart for config file changes to be detected, or restart the app automatically when it detects changes to the file, so I've seen people use databases. But it tends to be an overcomplication and it's usually turned out to be a bit of a pita. It's only worth it if you're regulalrly turning the feature on and off.<p>Many languages also support build flags, which strips the extra code out completely, but it's an obscure feature, unless you write libraries, that can confuse other programmers.
I usually avoid using third-party FF enablement services. Maybe 5 years ago it made more sense to use them, but as of 2020 I can't find good reasons anymore. They don't solve the right problem. Rolling your own FF enablement solution is cheap nowadays, it's much less hassle, much more robust, adjusted to your needs, and it's more privacy friendly.<p>KISS, you most likely don't need to use an external feature flag "hadron collider".
Like me who didn’t know about feature flags it is described here. [1]<p>[1] <a href="https://www.martinfowler.com/articles/feature-toggles.html" rel="nofollow">https://www.martinfowler.com/articles/feature-toggles.html</a>
Should you use a tool at all? One code file with the flags, and a small piece of router middleware that allows the URL to override the value of flags, and then just if statements. This has served me well on the past 3 frontend projects I have built.
This isn't a huge ordeal to DIY. A database table with some fields (name, on/off, dates) and a module to call that checks the db. A simple UI/API to CRUD those rows.<p>If it's a SaaS, how does your app function if the SaaS is unavailable?
We recently open sourced our platform, Bullet Train.<p><a href="https://github.com/BulletTrainHQ" rel="nofollow">https://github.com/BulletTrainHQ</a><p>We'd love feedback!