All Products
Search
Document Center

Microservices Engine:End-to-end canary release

Last Updated:Jun 08, 2026

This topic provides an overview of the tutorials on end-to-end canary release, helping you effectively use this feature.

Overview

Microservices Governance in Microservices Engine (MSE) supports end-to-end canary release across multiple integration types. This feature enables enterprises to conduct canary releases for microservices in a controlled manner, without altering the service versions in the existing production environment. It significantly mitigates the risks associated with canary releases and enhances canary release efficiency. Choose the tutorial that matches your gateway or pipeline setup.

Gateway-based tutorials

Use these tutorials if your entry point is a cloud-native gateway or an Ingress controller.

End-to-end canary release on frontend applications with MSE cloud-native gateways

Combine canary releases for frontend applications with monitoring and rollback policies to keep your system stable across continuous application updates. For more information, see Implement an end-to-end canary release on frontend applications based on MSE cloud-native gateways.

End-to-end canary release with MSE cloud-native gateways

MSE cloud-native gateways support end-to-end traffic management. Create routing rules to direct requests to specific application versions. For more information, see Implement an end-to-end canary release with an MSE cloud-native gateway.

End-to-end canary release with ALB Ingress

Application Load Balancer (ALB) Ingress provides flexible routing capabilities. Use ALB Ingress to run canary releases without modifying your business code. For more information, see Configure end-to-end canary release with an ALB gateway.

CI/CD pipeline-based tutorials

Use these tutorials if you are running deployments through a CI/CD pipeline.

End-to-end canary release with Jenkins CI/CD pipelines

Use Jenkins CI/CD pipelines to automate an end-to-end canary release. Based on canary testing results, gradually shift more live traffic to the new version or roll back to the stable version and troubleshoot. For more information, see Implement an end-to-end canary release by using Jenkins CI/CD pipelines.

Message queue-based tutorials

Use this tutorial if your microservices communicate through a message queue.

End-to-end canary release with ApsaraMQ for RocketMQ

Implement an end-to-end canary release based on ApsaraMQ for RocketMQ without modifying your business code. For more information, see End-to-end canary release with RocketMQ.