Feature Flag

Origin & evolution

The pattern was popularised by Flickr. In 2009 Ross Harmes described their approach in Flipping Out on the Flickr developer blog: the team committed everything to a single trunk and pushed to production many times a day, so they needed a way to turn features off in production without reverting code. The flag was the answer, and dark launching, shipping a feature to production switched off so it could be exercised under real load before anyone saw it, came from the same lineage.

Martin Fowler's article Feature Toggles, written with Pete Hodgson, did the conceptual work of naming the categories that matter. It distinguished release🚢ReleaseProduct SpecificationA shipped version of the productView reference → toggles (short-lived, for managing in-progress work), experiment🧫ExperimentValidationA test designed to validate a hypothesisView reference → toggles (for A/B tests), ops toggles (for operational control such as circuit breakers), and permission toggles (for entitlements). The crucial insight🔦InsightUser ResearchA synthesised finding from researchView reference → was that these have very different lifespans, and treating a permission flag like a release flag is how a codebase drowns in stale conditionals.

The field has since industrialised around managed platforms and a clear discipline: flags carry a cost, the conditional branches they create are technical debt, and short-lived flags must be removed once the rollout completes. The live tension is between the control flags give you and the complexity they accumulate if you never clean them up.

How it works in practice

A team building a redesigned checkout wraps it in a flag, new-checkout, defaulted off, and deploys the code to production where it sits dormant. They enable it for internal staff, then 1 percent of traffic, watching the checkout error-rate monitor at each step. At 1 percent a payment edge case surfaces; they flip the flag off in seconds, no deploy, no rollback, and fix the bug🐛BugProduct SpecificationA defect or unexpected behaviourView reference →.

Re-enabled, the rollout climbs to 5, then 25, then 100 percent over a week. Once it is fully on and stable, the flag and its dead else branch are deleted in the next sprint, because a release flag that outlives its release is a trap waiting for the next reader. The deploy happened once, early; the release happened gradually, under control.

Feature flag vs. its neighbours

• Deployment📤DeploymentEngineeringA deployment eventView reference → puts a version of code into an environment. A feature flag decides whether code that is already deployed is active. The flag is precisely the seam that lets you deploy on Tuesday and release on Friday.
• Experiment is a structured test comparing variants🆎VariantGrowthA variant in an A/B testView reference → to learn something, with a hypothesis🧪HypothesisValidationA testable belief about a solutionView reference → and a measured outcome🏆OutcomeStrategyA desired business or user outcomeView reference →. A flag is the delivery mechanism an experiment often rides on. Every experiment toggle is a flag; not every flag is an experiment.
• Feature is the product capability💪CapabilityStrategyAn ability that enables value deliveryView reference → itself. The flag is the gate in front of it. One feature is gated by one flag during rollout; after cleanup the feature remains and the flag is gone.

In the graph

In the Unified Product Graph, feature_flag🎌Feature FlagEngineeringA feature toggle for controlled rollout is a leaf in the Engineering and Platform region, anchored by the service⚙️ServiceEngineeringA deployable service or microserviceView reference →, with engineering as its home domain. The hierarchy edge service_toggles_feature_flagServicetogglesFeature Flaghierarchy ties the flag to the service whose behaviour it controls, and the cross-domain edge feature_flag_gates_featureFeature FlaggatesFeaturecross-domain reaches into Product and Delivery to connect the runtime switch to the user-facing capability it guards. Those two edges hold the whole idea in place: the flag belongs to engineering, the thing it gates belongs to product, and the edge between them is exactly the release-versus-deploy seam the concept exists to create.