|
|
|
|
|
by simplecomplex
2537 days ago
|
|
Ditto. One must already be using a database, so just add a table for features that you flip off and on. How could that possibly be more work than integrating API calls to a third party service just to ascertain a few (mostly unchanging) values? |
|
- not necessarily using/in control of db - audit log of who toggled which features and when - reporting on users exposed to each feature - A/B test support - toggle features without touching production database - ...