Change release policies
Use traffic allocation and deployment strategies such as blue-green deployment, A/B testing, and canary release to gradually roll out new application versions and enable quick rollbacks.
Release policies gradually switch production traffic to a new application version through controlled traffic allocation and deployment strategies. Phased releases and quick rollbacks minimize the impact of unexpected deployment issues. Common release policies include the following:
-
Blue-green deployment: Deploys a redundant new version of a service, typically with the same instance type and count as the old version. After the new version is validated, all traffic switches to it while the old version remains on hot standby. If issues arise, traffic switches back to the old version for a fast rollback.
-
A/B testing: Routes traffic to a new version based on user request metadata such as HTTP headers and cookies. By directing specific requests or users to the new version, this policy limits the potential blast radius of failures.
-
Canary release: Gradually shifts traffic from the old version to the new version by adjusting traffic weight, while scaling in the old version and scaling out the new version. This approach provides higher resource utilization than blue-green deployment.
Alibaba Cloud MSE Cloud-native Gateway is a managed traffic ingress with extensive traffic governance capabilities. It supports multiple service discovery methods, including Container Service, MSE Nacos, MSE Zookeeper, EDAS registry, SAE registry, fixed addresses, and DNS domain names. Through a unified model, the gateway supports different service editions and all three release policies described above, along with seamless application publishing and unpublishing.