Understanding a rollout
Throughout the first three chapters of this book, I have explained how using feature management can help reduce the risk of releasing new features to production, and how new implementations can be proven to be effective before getting released to 100% of customers. Rolling out a feature is how we can achieve this.
There are two types of rollouts: percentage and ring. You might have heard of this type of feature management being referred to as a progressive rollout, since a feature progresses either through an incremental percentage of customers or through various rings (or groups) of customers. We will look at both of these approaches to understand their value and uses.
One thing to be aware of with rollouts is that they are usually intended to be temporary. The name implies that this approach to feature management is just about getting something rolled out and once that is achieved, the feature flag's encapsulation can be removed from the code base...