This topic describes how to use Microservices Governance of Microservices Engine (MSE), including end-to-end canary release, traffic protection, and migration of Application High Availability Service (AHAS) traffic protection to MSE.
Introduction
End-to-end canary release
You can implement the following capabilities based on the end-to-end canary release feature of Microservices Governance:
You can use the new version of the end-to-end canary release feature in the updated Cloud-native Gateway.
Canary release of frontend applications can help maintain high performance and high stability of frontend applications along with 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.
You can use Jenkins to build continuous integration and continuous deployment (CI/CD) pipelines and implement an end-to-end canary release by using the CI/CD pipelines. You can determine the subsequent operations based on the canary release results. For more information, see Implement an end-to-end canary release by using CI/CD pipelines in Jenkins.
You can implement an end-to-end canary release based on ApsaraMQ for RocketMQ. ApsaraMQ for RocketMQ is used to provide asynchronous throttling. For more information, see Implement an end-to-end canary release based on ApsaraMQ for RocketMQ.
You can implement an end-to-end canary release based on APISIX Ingress gateways.
You can implement an end-to-end canary release based on Alibaba Cloud Application Load Balancer (ALB) Ingress gateways and the end-to-end canary release capability provided by MSE. For more information, see Configure an end-to-end canary release based on ALB Ingress gateways.
You can implement an end-to-end canary release based on MSE cloud-native gateways. This helps you implement end-to-end traffic throttling. For more information, see Implement an end-to-end canary release based on MSE cloud-native gateways.
You can implement an end-to-end canary release by using CI/CD pipelines that are automatically created by Alibaba Cloud DevOps.
Migration of AHAS traffic protection to MSE Microservices Governance
The traffic protection module of AHAS will be phased out soon. If you are an existing user of the traffic protection module, you can migrate the module to MSE Microservices Governance.
Traffic protection
You can implement the following capabilities based on the traffic protection feature of Microservices Governance.
You can implement graceful start and shutdown of microservice applications by using MSE Microservices Governance to prevent traffic loss during the release. You only need to enable Microservices Governance for your application and enable the graceful start and shutdown features for the application. Then, you can view the relevant visibility data of the application on the Application overview page. For more information, see Implement graceful start and shutdown of microservice applications by using MSE.
MSE traffic protection metrics and traffic protection events can be reported to Simple Log Service. You must install Logtail and configure the data source of Simple Log Service. Sentinel logs are collected, parsed, and reported to Simple Log Service. After the metric data is reported to Simple Log Service, you can create related charts by using query and analysis statements of Simple Log Service based on your business requirements. For more information, see Report MSE traffic protection metrics to Simple Log Service and Report MSE AHAS traffic protection events to Simple Log Service.
After traffic protection events are recorded in Simple Log Service, you can collect and analyze logs in real time and configure custom alert rules based on your business requirements. When the system log traffic exceeds the preset threshold, Simple Log Service automatically sends an alert notification to O&M personnel to quickly respond to burst traffic and abnormal traffic. This ensures the stability and security of applications. For more information, see Configure a traffic protection alert based on Simple Log Service.