Chapter 3. Best Practice #1: Maintain Flag Consistency
Our hypothetical ecommerce company, acmeshopping.com, has a landing page in one of the main sections of the web portal where customers can search and see search results, as they look for items they would like to buy. Sometimes, Acme’s customers search without buying. Often, users return and search again for the same items, and eventually some of them do a checkout. Acme is trying to reduce the time it takes users to find those frequently searched items by adding a new header section showing these items. Let’s call them “Previously Seen Products.”
This new section is gated by a feature flag named new_search_relevance. So, when new_search_relevance is enabled, the web portal will first display the “Previously Seen Products” section at the top of the search result part of the page.
You, as the person in charge of the rollout, set up this new feature to initially be seen by 10% of the user population. Exposing the feature from zero to a subset of the population is often called ramping up a feature. Here, a feature was ramped to 10%.
As demonstrated in Figure 3-1, the expectation is that if user A visits your site and your feature-flagging system decides that user A should see this feature (variation “on” of the feature), user A should then continue to see this same variation of the feature no matter how many times the flag is evaluated, assuming no external changes have occurred (for example, the flag definition changed).
Increasing ...
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