Deployment Strategy
Last updated
Was this helpful?
Last updated
Was this helpful?
With blue-green deployment, we have two identical environments: one is staging (blue) and the other is production (green).
After the new version has been tested and certified to meet all the requirements, the load balancer automatically switches the traffic from the older version to the newer version.
Compared with other strategies, it is easy to rollback but all user can access to the new version at the same time
In canary deployment, the deployment team sets up the new version and then gradually shifts the production traffic from the older version to the newer version.
Canary deployment enables better performance monitoring. It also aids in a faster and better rollback of the software if the new version fails. However, it has a slow nature and a more time-consuming deployment cycle.
In A/B testing deployment, developers deploy the new version alongside the older version. However, the new version is only available to a subset of users.
These users are selected based on specific conditions and parameters the engineers choose. These parameters can be the user’s location, type of device, UI language, and operating system.
This method measures the effectiveness of the application’s new functionality. After gathering statistics from performance monitoring
Based on the data, the better version will be identified
