3 ms·
But why do you need an external service for that? Isn’t that basically a single DB table with a name and an on/off value for each flag (or maybe an integer for
by echoangle 2y ago
But why do you need an external service for that? Isn’t that basically a single DB table with a name and an on/off value for each flag (or maybe an integer for multiple options)?
- hobofan 2y agoIn it's simplest incarnation, yes it could be just a single DB table with boolean flags. However there are a lot of connected needs that most real world-usages run into: - Per-user toggles of configuration values - Per-user dynamic evaluation based on a set of rules - Change history, to see what the flag value was at time of an incident - A/B testing of features and associated setting of tracking parameters - Should be controllable by e.g. a marketing/product manager and not only software engineers That can quickly grow into something where it's a lot easier to reach for an existing well thought out solutions rather than trying to home-grow it.
- random_kris 2y agoIn microservice world. Do you want to track features in each service or have a source of truth using flagd I prefer central source of truth
- jacobr1 2y agoIn a microservice world obviously you'd have a feature-flag service. But you still have a build/buy consideration.
- j45 2y agoGreat summary. The more parties involved with more and more configurations the more management of details is needed.