How to make a canary release strategy with A/B testing
One of the strategies used when you want to release functionality without running the risk that an error in the new functionality interrupts the application is to expose the functionality to a small group of users in the live environment. Then, you observe its behavior and determine whether the behavior is as expected. If an error is detected, the previous functionality is simply exposed again to all users by reverting to the previous version. Otherwise, if its behavior is correct, the new functionality is exposed to more and more users until it reaches 100% of users. This is called the canary release strategy:
Figure 4.9 – Canary release
Static versus dynamic data considerations
When implementing the canary release strategy, it is important to understand the type of data that will be exposed by our new service, in order to control possible version update problems that may occur due to external...
