Loading content
Feature flags are a powerful tool to enable or disable features independently of a release version. This enables agile development and testing of new functionalities in the production environment while minimizing risk.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Feature flags are runtime-evaluated switches that let software features be turned on or off independently of the deploy state.
The approach emerged from the need to ship new functionality in a controlled way without long-lived branches or full code changes. In a 2017 article on Martin Fowler's site, Pete Hodgson describes feature toggles/flags as a pattern for switching behavior at runtime, testing internally first, and then releasing gradually through canary or A/B experiments.
Think of a feature flag as a decision layer in front of a code path. The code contains multiple possible behaviors; at runtime, a flag source decides which one is active for a request, user, or cohort. The new path can stay deployed but hidden, selectively enabled, or quickly rolled back without rebuilding the rest of the system.
Whether a feature is active is determined while the system runs, not only at build or release time.
User groups or requests can be treated differently, for example for internal testing or gradual rollout.
Code can be deployed before the feature becomes visible to everyone.
Controlled switching supports iterative work and smaller, lower-risk changes.
Incremental release, observation, and controlled expansion are enabled technically.
Old and new behavior must work safely in parallel while a flag routes traffic.
Feature flags are useful for gradual releases, canary rollouts, experiments, and quickly disabling a new feature. They matter most when deployments are frequent, risk must be contained, or different audiences should see different variants. The trade-off is added complexity: flags need documentation, testing, and eventual removal, otherwise technical debt and confusing states accumulate.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.