Enable dynamic toggling of software features to control release, experimentation, and risk mitigation.

To discuss or refer to the practice of using feature flags for controlling feature availability in software.

When releasing new features behind a flag, conducting A/B tests, performing canary releases, or needing quick rollback.

Software development, release management, experimentation platforms, DevOps pipelines.

feature flag pattern

feature flag: [feature_name] = [on/off]

{feature_name}, {flag_name}, {state: on/off}

• LaunchDarkly
• Unleash
• ConfigCat
• canary release
• A/B testing
• trunk-based development

• Feature branches (higher merge risk and longer feedback loops)
• dark launches (no user opt-in)
• permission/gating systems (more heavyweight)

Using flags as permanent technical debt → accumulation of stale flags increases complexity;\nPlacing flag checks in hot paths without consideration → added latency can affect performance;\nNesting multiple flags without clear hierarchy → combinatorial explosion of states making testing difficult;\nFailing to retire stale flags → technical debt and confusion about which flags are active.

Feature branching: long-lived branches for isolation vs flags for trunk‑based development;\nCanary release: gradual traffic shift via infrastructure vs flag‑controlled rollout;\nDark launch: deploying features to users without their knowledge vs explicit opt‑in via flags.

Coming from feature branching workflows: may treat flags as long‑lived branches → treat flags as short‑lived toggles and retire them promptly;\nComing from release‑train processes: may rely on scheduled releases instead of instant toggles → use flags for immediate on/off control.

• feature toggles
• release toggles
• canary releases
• dark launches

Avoid using flags as a substitute for proper modular design; flag checks add negligible latency but excessive checks in hot paths can add measurable overhead; nested or numerous flags create combinatorial complexity and make testing difficult—stale flags must be cleaned up to prevent technical debt.

Enables safe, controlled rollouts and instant rollbacks without redeployment, reducing risk and enabling experimentation.

Think of a feature flag as a light switch for a software feature—flip it on or off instantly without redeploying.

Progressive delivery frameworks (e.g., Argo Rollouts, Flagger) for automated canary analysis and promotion.