This topic provides instructions for the microservice governance module, covering application registration, service search, application governance, end-to-end canary release, development and testing governance, and system settings.
Application integration
MSE microservice governance supports multiple connection types. Choose a connection type based on your application’s deployment environment and programming language.
Microservice namespace management
A microservice namespace is an extensible policy used to organize a group of microservices, making them easier to manage and distribute. It provides a way to group microservices and their dependencies, enabling teams to assign different security policies, access controls, and resource limits. For more information, see Microservice namespace management.
Register Java-based microservice applications in ACK and ACS with the MSE governance center
You can register Java-based microservice applications, such as Spring Cloud and Dubbo applications, deployed in Container Service for Kubernetes (ACK) and Container Compute Service (ACS), with the MSE governance center. For more information, see Register Java-based microservice applications in ACK and ACS with the MSE governance center.
Register Go-based microservice applications in ACK with the MSE governance center
You can register Go-based microservice applications, such as Gin applications, deployed in ACK, with the MSE governance center. For more information, see .
Register microservice applications on ECS instances with the MSE governance center
You can register applications deployed on ECS instances and on-premises virtual machines with the MSE governance center. For more information, see Register microservice applications on ECS instances with the MSE governance center.
Register applications in open source Kubernetes clusters with the MSE governance center
You can register Spring Cloud and Dubbo applications deployed in open source Kubernetes (K8s) clusters with the MSE governance center. This provides features such as graceful shutdown, outlier ejection, service search, service authentication, service testing, and canary release, which significantly improve the stability and development efficiency of your online microservices. For more information, see Register applications in open source Kubernetes clusters with the MSE governance center.
Add a custom API in microservice governance
You can register an application with MSE microservice governance using custom software development kit (SDK) instrumentation combined with a Java agent. For more information, see Add a custom API in microservice governance.
Network configuration for connecting to microservice governance from an on-premises environment
For information about how to configure your network to connect to MSE microservice governance from an on-premises environment, see Network configuration for connecting to microservice governance from an on-premises environment.
Service search
The service search feature of microservice governance lets you view details and service contracts of registered application services.
Search for services
After registering your services with MSE microservice governance, you can use the MSE console to query the service list and details for your deployed Spring Cloud or Dubbo applications. For more information, see Search for services.
Search for service contracts
A service contract is a document that describes the API and behavior of a service. In MSE, a service contract defines the communication rules between a service provider and a consumer and may include information about the service’s inputs, outputs, and fault handling. This helps consumers better understand and use the service. For more information, see Search for service contracts.
Application governance
Applications registered with MSE microservice governance can use traffic governance features, including graceful shutdown and startup, system protection configuration, traffic protection, tag-based routing, and message canary release.
Application overview
After registering a service with MSE microservice governance, you can view metrics such as queries per second (QPS) and TOP lists for the application on the Application Overview page in the MSE console. For more information, see Application overview.
API details
The API Details page displays comprehensive information for all APIs of the application, including statistics such as QPS, response time (RT), and concurrent requests. Click the tabs for different types to access details for each API type, such as web services and RPC services. For more information, see API details.
Node details
The Node Details feature lets you view basic information for all nodes under an application, including statistical data such as QPS and node metadata such as tags and statuses. For more information, see Node details.
Traffic governance
Traffic governance is primarily used for traffic control to achieve load balancing and fault tolerance across microservice instances. It provides features such as peak-load shifting and throttling to ensure high availability and concurrent processing capabilities. For more information, see Traffic governance.
End-to-end canary release
Canary release distributes traffic across multiple versions, enabling iteration and maintenance without affecting the production system. MSE lets you implement end-to-end canary releases down to specific microservice instances, providing fine-grained traffic control and more accurate assessment of microservice quality and stability.
Implement an end-to-end canary release using an MSE cloud-native gateway
After registering an application with microservice governance, you can configure an MSE cloud-native gateway to implement an end-to-end canary release. Use the cloud-native gateway to expose backend services. For more information, see Implement an end-to-end canary release using an MSE cloud-native gateway.
End-to-end canary release based on MSE Ingress
An MSE Ingress gateway is an Ingress traffic management method based on the MSE cloud-native gateway. The end-to-end canary release capability provided by the MSE Ingress gateway enables end-to-end traffic control without modifying any business code. For more information, see End-to-end canary release based on MSE Ingress.
Implement an end-to-end canary release using a self-managed Spring Cloud Gateway or Zuul gateway
If your microservices model uses Spring Cloud Gateway or Zuul as the API gateway, you can configure routing rules to direct requests to a canary environment, allowing you to validate and test the canary release version. For more information, see Implement an end-to-end canary release using a self-managed Spring Cloud Gateway or Zuul gateway.
Implement an MSE-based end-to-end canary release with Kruise Rollouts
Kruise Rollouts provides multiple phased release strategies, such as canary release and blue-green deployment. By integrating with MSE microservice governance, Kruise Rollouts enables smooth canary upgrades for new application versions throughout the service invocation chain, ensuring the stability of the new versions. For more information, see Implement an MSE-based end-to-end canary release with Kruise Rollouts.
Support for asynchronous tasks in MSE end-to-end canary release
MSE supports traffic tag pass-through for custom asynchronous tasks. To enable this functionality, add an asynchronous pass-through scan package. For more information, see Support for asynchronous tasks in MSE end-to-end canary release.
System settings
Manage the settings of MSE microservice governance as needed.
Upgrade MSE microservice governance components
MSE microservice governance components have been updated. Upgrade the legacy ack-mse-pilot component to the ack-onepilot component. For more information, see Install and upgrade MSE microservice governance components.
Disable MSE microservice governance
If your application no longer uses the features of the MSE governance center, disable MSE microservice governance. For more information, see Disable MSE microservice governance.