A/B Testing Flag
A feature flag used to split traffic between different versions of a feature for experimentation and optimization purposes.
Related:
Experiment FlagPercentage Rollout
Feature Flag Glossary
Your comprehensive guide to feature flag terminology, from basic concepts to advanced patterns
A
C
Canary Release
A deployment strategy where new features are gradually rolled out to a small subset of users before full release, controlled by feature flags.
Related:
Progressive RolloutStaged Rollout
Circuit Breaker Pattern
A feature flag pattern that automatically disables features when they fail, preventing cascading failures in production systems.
Related:
Kill SwitchEmergency Flag
D
Dark Launch
Deploying new code to production without making it visible to users, controlled by feature flags for testing in real production environments.
Related:
Silent ReleaseShadow Testing
Dead Code
Code that is never executed because the controlling feature flag has been permanently disabled or the feature has been fully rolled out.
Related:
Stale CodeTechnical Debt
E
Environment-Specific Flag
Feature flags configured differently across development, staging, and production environments for environment-specific behavior.
Related:
Configuration FlagEnvironment Toggle
Experiment Flag
A temporary feature flag used to conduct controlled experiments and measure the impact of new features on user behavior.
Related:
A/B Testing FlagMultivariate Testing
F
Feature Flag
A software development technique that allows teams to enable or disable functionality without deploying new code, also known as feature toggles.
Related:
Feature ToggleFeature Switch
Feature Flag Debt
The accumulated cost and complexity from maintaining obsolete or unnecessary feature flags in a codebase over time.
Related:
Technical DebtFlag Sprawl
Feature Flag Lifecycle
The stages a feature flag goes through from creation to removal: development, testing, rollout, full deployment, and cleanup.
Related:
Flag ManagementFlag Retirement
Flag Configuration
The settings that determine how a feature flag behaves, including targeting rules, percentage rollouts, and default values.
Related:
Flag RulesTargeting Configuration
Flag Retirement
The process of removing feature flags and their associated code branches after they are no longer needed.
Related:
Flag CleanupDead Code Elimination
Flag Sprawl
The uncontrolled proliferation of feature flags in a codebase, leading to increased complexity and maintenance burden.
Related:
Feature Flag DebtTechnical Debt
K
Kill Switch
An emergency feature flag that can instantly disable problematic features in production to prevent system failures or data corruption.
Related:
Circuit BreakerEmergency Toggle
L
LaunchDarkly
A popular feature flag management platform that provides SDKs, APIs, and a dashboard for controlling feature releases across applications.
Related:
Feature Management PlatformFlag Service
Long-Lived Flag
A feature flag intended to remain in the codebase indefinitely, such as kill switches or operational toggles.
Related:
Permanent FlagOps Toggle
M
Multivariate Flag
A feature flag that can have multiple values beyond simple on/off states, enabling complex feature variations and experiments.
Related:
Multi-Value FlagVariant Flag
O
Operational Toggle
A long-lived feature flag used for operational control, such as rate limiting, maintenance modes, or performance tuning.
Related:
Ops FlagSystem Toggle
P
Percentage Rollout
A feature flag configuration that enables features for a specific percentage of users, allowing gradual feature deployment.
Related:
Progressive RolloutGradual Release
Permission Toggle
A feature flag that controls access to features based on user permissions, roles, or subscription levels.
Related:
Access FlagEntitlement Flag
Progressive Rollout
The practice of gradually increasing the percentage of users who receive a new feature, monitored and controlled by feature flags.
Related:
Staged RolloutPhased Release
R
Release Toggle
A temporary feature flag used to control the release of new features, typically removed after successful deployment.
Related:
Release FlagDeployment Flag
Remote Configuration
The ability to change feature flag states without code deployment, typically through a management dashboard or API.
Related:
Dynamic ConfigurationRuntime Control
S
Split.io
A feature flag and experimentation platform that combines feature management with analytics for data-driven releases.
Related:
Feature Management PlatformExperimentation Platform
Stale Flag
A feature flag that is no longer serving its intended purpose, often at 100% rollout or 0% for extended periods.
Related:
Obsolete FlagDead Flag
T
Targeting Rules
Conditions that determine which users or segments receive specific feature flag variations based on attributes like location, device, or behavior.
Related:
User TargetingSegmentation Rules
Technical Debt
The implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.
Related:
Code DebtFeature Flag Debt
Toggle Point
The specific location in code where a feature flag decision is made, determining which code path to execute.
Related:
Decision PointBranch Point
Trunk-Based Development
A development practice where all developers work on a single branch, using feature flags to control feature visibility instead of long-lived branches.
Related:
Continuous IntegrationFeature Flagging
U
Unleash
An open-source feature flag management system that provides a web UI and client SDKs for controlling feature toggles.
Related:
Feature Management PlatformOpen Source Flagging
User Targeting
The practice of enabling features for specific users or user segments based on attributes like ID, email, or custom properties.
Related:
User SegmentationTargeted Rollout
V
Variant
One of multiple possible values or configurations that a multivariate feature flag can return.
Related:
Flag ValueFeature Variation
Stop Feature Flag Debt from Growing
FlagShark automatically identifies and removes stale feature flags, saving your team hours every week.