Microservice administration

End-to-end canary release

The following tutorials cover end-to-end canary releases:

• The cloud-native gateway supports a new end-to-end canary release feature. For more information, see Migration to the new end-to-end canary release of the cloud-native gateway.

• Frontend phased release helps frontend applications maintain high performance and stability during iterative updates. For more information, see Implement frontend phased release using the MSE cloud-native gateway.

• Build a Jenkins CI/CD pipeline for end-to-end canary releases and make decisions based on canary validation results. For more information, see Implement microservice end-to-end canary release by building a CI/CD pipeline with Jenkins.

• Implement end-to-end canary releases for traffic shaping in asynchronous message queue scenarios. For more information, see Implement end-to-end canary release based on Message Queue for Apache RocketMQ.

• Implement an end-to-end canary release by using the flexible routing feature of Ingress-APISIX. For more information, see Implement end-to-end canary release based on an Ingress-APISIX gateway.

• Combine the flexible routing feature of Alibaba Cloud Application Load Balancer (ALB) with MSE to implement end-to-end canary releases. For more information, see Configure end-to-end canary release based on an ALB gateway.

• Implement end-to-end canary releases by using the MSE cloud-native gateway. For more information, see Implement end-to-end canary release using the MSE cloud-native gateway.

• Build a CI/CD pipeline with Apsara DevOps for microservice end-to-end canary releases. For more information, see Implement microservice end-to-end canary release by building a CI/CD pipeline with Apsara Devops.

Migrate AHAS traffic protection to MSE microservice administration

The AHAS traffic protection module is being deprecated. Migrate to MSE microservice administration. For more information, see Migrate AHAS traffic protection to MSE microservice administration.

Traffic protection

The following tutorials cover traffic protection:

• Implement lossless online and offline publishing to prevent traffic loss. Connect your application to the MSE administration center, enable lossless publishing, and view observable data on the overview page. For more information, see Implement lossless online and offline publishing for microservice applications using MSE.

• Report MSE traffic protection metrics and events to Simple Log Service (SLS). Enable the collection component, set the SLS ingestion data source, and build charts by using SLS query analysis statements. For more information, see Report MSE traffic protection metrics to SLS and Report MSE traffic protection events to SLS.

• After traffic protection events are recorded in Simple Log Service (SLS), configure alerting rules based on real-time log analysis. SLS sends alert notifications to O&M engineers when traffic exceeds preset thresholds, enabling quick responses to burst or unusual traffic. For more information, see Traffic protection alerting based on SLS.