This topic provides an overview of the tutorials on end-to-end canary release, helping you effectively use this feature.
Overview
The end-to-end canary release feature provided by Microservices Governance enables enterprises to conduct canary releases for microservices in a controlled manner, without altering the service versions in the existing production environment. This feature significantly mitigates the risks associated with canary releases and enhances canary release efficiency. For information about how to implement end-to-end canary releases, see the following tutorials.
Implement an end-to-end canary release on frontend applications based on MSE cloud-native gateways
You can use canary releases for frontend applications, combined with monitoring and rollback policies, to create a powerful mechanism that ensures system stability. The coordination of the three policies can help maintain high performance and high stability throughout the continuous iterations and updates of the applications. For more information, see Implement an end-to-end canary release on frontend applications based on MSE cloud-native gateways.
Implement an end-to-end canary release by using Jenkins CI/CD pipelines
You can use Jenkins CI/CD pipelines to implement an end-to-end canary release. Based on canary testing results, you can determine the subsequent steps you need to perform. If the new version is proven to be stable, gradually shift more live traffic to the new version until it serves all live traffic. If issues are found in the new version, roll back to the original version and troubleshoot the issues. For more information, see Implement an end-to-end canary release by using Jenkins CI/CD pipelines.
Implement an end-to-end canary release based on ApsaraMQ for RocketMQ
You can implement an end-to-end canary release based on ApsaraMQ for RocketMQ without modifying your business code. For more information, see Implement an end-to-end canary release based on Message Queue for Apache RocketMQ.
Configure an end-to-end canary release based on ALB Ingress gateways
Alibaba Cloud Application Load Balancer (ALB) Ingress gateways provide flexible routing capabilities. You can use ALB Ingress gateways to facilitate canary releases without modifying your business code. For more information, see Configure an end-to-end canary release based on ALB Ingress gateways.
Implement an end-to-end canary release based on MSE cloud-native gateways
Microservices Engine (MSE) cloud-native gateways can help you implement end-to-end traffic management. You can create rules to direct requests to specific application versions. For more information, see Implement an end-to-end canary release based on MSE cloud-native gateways.