Feature flag
A feature flag switches planned application behaviour through configuration. It can separate technical deployment from making a feature available.
A feature flag is a configurable switch for planned application behaviour. The program code must evaluate it and provide suitable paths for its enabled and disabled states.
A hypothetical portal initially makes a new repeat-order feature available only to a test group. The new code can already be running while other users retain the previous flow. The group receiving the feature is defined explicitly.
Disabling it does not undo orders already created or database changes. A feature flag is also no substitute for access-right checks. The team should test both states and remove switches that are no longer needed so old conditions do not remain unnoticed in the code.
Sources
Related terms
- Software releaseA software release is an identified software version made available for a particular use. Publishing it does not automatically switch every system to it.
- Continuous deliveryContinuous delivery prepares software changes for release through a repeatable process. Approval for production can remain a deliberate decision.
- Cache stampedeA cache stampede occurs when concurrent cache misses trigger the same expensive calculation or data query repeatedly.
- BackpressureBackpressure adjusts incoming data to the receiver’s processing capacity through signals to slow down or pause.
- Race conditionA result depends on the timing of overlapping accesses and can therefore be wrong.
- Memory leakMemory that is no longer needed stays allocated while the program runs.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.