Observability Glossary

Blue Green Deployment

Blue Green Deployment is a technique used to minimize downtime and risk when releasing a new version of an application. With Blue Green Deployment, you have two identical production environments, referred to as "blue" and "green." At any given time, only one of these environments is live and serving user traffic, while the other remains idle. When a new version of the software is ready to be deployed, it is released to the idle environment. Once the new version is successfully deployed and tested, traffic is switched to the updated environment, making it live, while the previous version becomes idle.

This strategy ensures that users experience minimal disruption during updates and provides a straightforward rollback mechanism in case any issues arise with the new version.

Explore related concepts

Zero-Downtime Deployment

Zero-Downtime Deployments are the process of updating an application without causing any disruption to the end users. This is achieved by gradually shifting user traffic from the old version to the new version, ensuring a transition without disrupting the live service.

Canary Release

A deployment strategy that enables rolling out new features to a small subset of users before releasing them to the entire user base. This method helps to mitigate risks by testing the new functionality in a production, enabling you to monitor its performance and stability before a full release.

Continuous Deployment

The practice of automatically deploying code changes to production as soon as they are ready, without the need for manual intervention.