Have a naming convention for short or long term flags
Use meaningful names with long descriptions
Have a central location for flags, one place to look at available flags
The development team should share flags and configurations at the end of a sprint so that the right configuration is released.
NEVER re-purpose a feature flag
Deprecate unused features and their flags
Knight Capital and Feature Flags
In 2012, Knight Capital Group suffered a trading loss of $440 million in 45 minutes due to a software glitch.
The glitch was caused by the release of new software code that was not fully tested before being deployed to production.
The code included an old feature that had been previously disabled, but was inadvertently reactivated by the new release.
DATA - SQL/JSON Models
Be additive, never change existing fields
If you have to remove a field, obsolete it until there is no possibility of rollback
Separate the data model from the business logic
Feature Flag Providers
Azure App Configuration
Launch Darkly
Split
Optimizely
Molasses
Flagship
GrowthBook
Apptimize
Taplytics
Harness
OpenFeature
OpenFeature is an open standard for feature flag management. OpenFeature provides a unified API and SDK, with extensibility for open source and commercial offerings.