Looking at the list of Alternatives

[alber70g]

When looking at the list of alternatives, have you looked into all these implementations of feature toggles?
Is it possible that you provide a short con/pro of each implementation?

[mexx]

Hello @alber70g,

as mentioned in the section Why this library I've looked deeply into the first three mentioned alternatives. The section explains, at least I hope so, the backgrounds of the design decisions.

Other alternatives I've added for completion once detected, as far as this list can be complete ;)
After FeatureSwitcher was born, I really had no need to look deeply into the alternatives.

[alber70g]

Thanks you for your answer. I've got another question: do you also have something in place to store feature toggles in the database? Or is that something I have to do myself?

[malaqueueit]

We have build a plugin that uses Amazon AWS DynamoDB/API Gateway as backend. If you do not want to use that, then you can look at our code as a reference on how to build your own plugin. https://github.com/queueit/FeatureSwitcher.AwsConfiguration

[mexx]

@alber70g in my use case there was already a database with configuration table present and I needed to control the features through this table. So for me it didn't seemed right to provide a standardized way to store feature configuration into a database. How ever one can easily write a behavior for it.

I don't know whether you've already looked into examples repository. There was recently a contribution to show how to store features in database. Please have a look at the code.

The AwsConfiguration plugin mentioned by @malaqueueit can also be used as inspiration on how to do it.