![]() ![]() This can lead to edge cases and bugs which can't be discovered until the code has been pushed to production. There are often small differences between the staging environment and production, no matter how much effort is made to make them identical. Blue-green deployment is a deployment strategy that can help with this goal by allowing more code pushes to production while lowering the risk of new releases. One of the goals of continuous integration (a DevOps technique) is to get software live as soon as possible and speed up the development process through automated testing and frequent code integration. ![]() Continuous integration/continuous delivery (CI/CD) Because there are two identical environments for production, if new changes are rolled out to one (say the blue version) and any issues are discovered, a router can just switch back to the other environment (green version) which has the old version of the code with zero downtime. One of the main benefits of blue-green deployments is disaster recovery. Blue-green deployment use cases Rollbacks Once the new changes have been tested in production, a router can then switch to point to the environment where the new changes are live, making for a smooth cut-over. The two production environments are kept as identical as possible, and when new code is deployed, it is pushed to the environment that is currently inactive. Blue-green deployment is a software development technique which utilizes two production environments (a "blue environment" and a "green environment") in order to make the software deployment process easier and safer. ![]()
0 Comments
Leave a Reply. |