Chapter 8. Best Practice #6: Scope Each Flag to a Single Team
In our previous example, acmeshopping.com was experimenting with offering free shipping for some orders via a feature-flag managing rollout. Marketing executives want to promote this new feature heavily and plan to put a banner at the top of the home page. Of course, we don’t want to show that banner to users who won’t be eligible for free shipping—we could end up with some grumpy customers that way! We need to place that banner behind a feature flag.
We could create a new feature flag called “free shipping banner,” and use that to manage the display of the banner ad. But we’d need to make sure that this banner wasn’t ever on when the other “free shipping” feature was off; otherwise, we’d be back to grumpy customers unhappy that they will not be getting the free shipping.
To avoid this problem, some feature-flagging systems allow you to “link” different flags together, marking one flag as a dependency of the other. However, most of the time there’s a much simpler solution: just use one flag to control both the feature and the banner promoting the feature!
Although this might seem like an obvious best practice, it’s sometimes not so obvious when flags are grouped by team, and the team implementing the shipping calculation code is very disconnected from the team implementing the banner ad. Ideally, your product delivery teams are already oriented around product features (i.e., the product detail page team, the search ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access