By reasonable traffic distribution and deployment strategies, production traffic can be gradually switched to the newly released application for gray release and quick rollback, maximizing the avoidance of impacts caused by unexpected change deployments. Widely used deployment strategies in the industry include:
Blue-Green Deployment: Implemented by redundantly deploying the new version of the service. Generally, the instance specification and quantity of the new version are kept consistent with the old version. When the new version service passes the verification, all business traffic will be switched to the new version. The old version will serve as a hot standby. If there are problems after the new version goes online, all traffic can be switched back to the old version for rollback, shortening the time for fault recovery.
A/B testing: Routing traffic to the new version based on the meta information of user requests. It is a gray release strategy based on request content matching. Common practices include using HTTP headers and cookies to gray-release specific requests or users to the new version, reducing the scope of faults.
Canary Release: Incrementally switching traffic from the old version to the new version by adjusting the traffic weight ratio. At the same time, the old version of the service is scaled down and the new version is scaled up. It has higher resource utilization compared to blue-green deployment.
Alibaba Cloud MSE Cloud-Native Gateway provides a hosted approach for traffic entry, providing rich traffic governance capabilities, supporting multiple service discovery methods such as container service, MSE Nacos, MSE ZooKeeper, EDAS registry center, SAE registry center, fixed address, and DNS domain names, and supporting service versions and gray release capabilities with a unified model. It supports the above three release strategies and features such as zero-loss application online/offline.