Comment by hobofan

In 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.