MSE Microservices Governance lets you connect applications, query services, apply traffic governance rules, run end-to-end canary releases, and manage component settings — all from a single governance center.
Connect applications
MSE Microservices Governance supports several connection methods. The right method depends on where your application runs and how it is built.
Manage microservice namespaces
A microservice namespace groups microservices and their dependencies so you can assign separate security policies, access controls, and resource limits to each group. For more information, see Manage microservice namespaces.
Connect Java microservice applications in ACK and ACS clusters to the MSE governance center
Connect Spring Cloud and Dubbo applications deployed in Container Service for Kubernetes (ACK) and Container Compute Service (ACS) clusters to the MSE governance center. For more information, see Connect Java microservice applications in ACK and ACS clusters to the MSE governance center.
Connect microservice applications on ECS instances to the MSE governance center
Connect applications deployed on Elastic Compute Service (ECS) instances and non-Alibaba Cloud virtual machines (VMs) to the MSE governance center. For more information, see Connect microservice applications on ECS instances to the MSE governance center.
Connect applications in open source Kubernetes environments to the MSE governance center
Connect Spring Cloud and Dubbo applications running in open source Kubernetes environments to get graceful shutdown, outlier ejection, service query, service authentication, service testing, canary release, and other governance features — without modifying business code. For more information, see Connect applications in open source Kubernetes environments to the MSE governance center.
Add custom interfaces to Microservices Governance
Instrument a Java application with the Java SDK and a Java agent to connect interfaces that MSE cannot auto-detect. For more information, see Add custom interfaces to Microservices Governance.
Network configuration for connecting to Microservices Governance from a non-Alibaba Cloud VPC
Configure network connectivity when your application runs in a virtual private cloud (VPC) outside Alibaba Cloud. For more information, see Network configuration for connecting to Microservices Governance from a non-Alibaba Cloud VPC.
Service query
After connecting your applications, use the service query feature to inspect service lists, call details, and contract definitions.
Query services
View service lists and details for your connected Spring Cloud or Dubbo applications directly in the MSE console. For more information, see Query services.
Query service contracts
A service contract describes the interfaces and behavior of a microservice. It defines the communication rules between a provider and a consumer, including input, output, and error-handling behavior. Reviewing contracts helps consumers understand and integrate a service correctly. For more information, see Query service contracts.
Application governance
For connected applications, apply traffic governance rules including graceful startup and shutdown, system protection, traffic throttling, tag-based routing, and canary release for messaging.
Application overview
View QPS data, top lists, and other real-time metrics for a connected application on the Application overview page in the MSE console. For more information, see Application overview.
Interface details
The Interface details page shows per-interface statistics — QPS, response time (RT), and concurrency — broken down by interface type (web services, RPC services, and more). For more information, see Interface details.
Node details
View basic information for every node of an application, including QPS statistics, tags, and status. For more information, see Node details.
Traffic governance
Use peak-load shifting and traffic throttling to maintain load balancing and fault tolerance across microservice instances under high concurrency. For more information, see Traffic governance.
End-to-end canary release
A canary release routes a controlled share of traffic to a new version of a service while the stable version continues to serve the rest. MSE extends this to the full service invocation chain — so a traffic tag applied at the gateway propagates automatically through every downstream microservice, letting you validate a new build end-to-end without touching production traffic.
Implement an end-to-end canary release based on an MSE cloud-native gateway
Use an MSE cloud-native gateway as the entry point to route canary traffic into connected backend services. For more information, see Implement an end-to-end canary release based on an MSE cloud-native gateway.
Implement an end-to-end canary release based on a cloud-native API gateway
Use a cloud-native API gateway with backend services deployed in an ACK cluster or registered with MSE Nacos to route canary traffic end-to-end.
End-to-end canary release based on an MSE Ingress
Use the MSE Ingress gateway's built-in traffic management to implement end-to-end canary releases without modifying business code. For more information, see End-to-end canary release based on an MSE Ingress.
Implement an end-to-end canary release based on a self-managed Spring Cloud Gateway or Zuul gateway
Configure routing rules on a self-managed Spring Cloud Gateway or Zuul gateway to send a portion of requests to a canary environment for verification. For more information, see Implement an end-to-end canary release based on a self-managed Spring Cloud Gateway or Zuul gateway.
Implement an MSE-based end-to-end canary release with Kruise Rollouts
Combine Kruise Rollouts phased release policies (canary release and blue-green deployment) with MSE Microservices Governance to roll out new application versions across the full service invocation chain while preserving stability. For more information, see Implement an MSE-based end-to-end canary release with Kruise Rollouts.
Asynchronous task support for MSE end-to-end canary release
Add a scan package to propagate traffic tags through custom asynchronous tasks, extending canary release coverage to async workloads. For more information, see Asynchronous task support for MSE end-to-end canary release.
System settings
Manage MSE Microservices Governance component settings, including upgrades and deactivation.
Upgrade the MSE Microservices Governance component
The older ack-mse-pilot component has been replaced by ack-onepilot. Upgrade to ack-onepilot to continue receiving governance features and updates. For more information, see Install and upgrade the MSE Microservices Governance component.
Disable MSE Microservices Governance
Disable the MSE governance center when your application no longer needs its features. For more information, see Disable MSE Microservices Governance.