Canary Release vs Feature Flags

A Canary Release is a deployment strategy used in software development to reduce the risk of introducing a new version by initially rolling it out to a small subset of users.

The name originates from miners who would carry a canary in a cage down coal mines. If toxic gases leaked into the mine, the canary would die before the miners..

The system is carefully monitored for issues, and if the new version performs well, it is gradually released to more users.

If issues are detected, the release can be rolled back, and the old version reinstated for all users.

Different strategies are used to select which users will be exposed to the new version, such as random sampling or selection based on demographics.

Feature Flags, also known as Feature Toggles, are a technique that allows developers to enable or disable certain functionalities in a software application without changing the codebase.

They can be implemented using boolean values in configuration files that are conditionally checked to determine whether a functionality should be visible and active or not.

They are used in Continuous Deployment (CD) approaches, Canary Releases, A/B Testing, and to manage the visibility of functionalities for different user segments.

Feature Flags allow for safer and more efficient development, enabling teams to deploy and test new features without impacting the entire user base.

The use of Feature Flags has grown in popularity with the rise of Agile, DevOps, and continuous delivery practices in software development.

They can be defined using a service like Bullet Train or Launch Darkly, creating a custom backend service, or using local files within the application.