liveBook · Manning

Feature flag

As explained in The AI Pocket Book

A configuration mechanism that controls which users see a given version of a feature.

A feature flag controls which users see a given version of a feature. It lets new code reach production without immediately exposing it to everyone. section 5.6

Release to a small group first

A team pushes new code to the main branch, then directs most users to the old version while exposing the new version only to the developer and quality-assurance team. After validation, it removes the old code and sends every user to the new version. section 5.6

Use the flag as part of a controlled delivery process:

  • Deploy the new implementation while keeping most users on the existing implementation. section 5.6
  • Expose the new implementation to a small validation group, check that it works, and switch everyone over only afterward. section 5.6
  • Pair the rollout with automated tests; the flag supports trunk-based development but does not replace validation. section 5.6

How The AI Pocket Book covers it

How deep it goes
Explains staged exposure and final switchover, but does not detail flag implementation or management.
Examples
Uses old-versus-new code paths, developers, and quality-assurance staff as the staged rollout example.
What it assumes
Assumes familiarity with production code and deployment, while connecting the practice to trunk-based development.
What you can do after
Operate/configure staged releases that validate new features before exposing them to every user.
How it connects
Connects feature flags with trunk-based development, automated testing, deployment pipelines, and quality assurance.

Also explained in

Compare how 8 books explain feature flag →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The AI Pocket Book. The section links point to the parts of the book it draws on.