Microservices Governance is a managed service governance platform within Microservices Engine (MSE). It adds traffic management, resilience, and release safety to Spring Cloud and Apache Dubbo applications without code changes, configuration edits, or image rebuilds.
How it works
Microservices Governance enhances mainstream open source microservices frameworks and applies governance policies defined in the MSE console. It also decouples middleware from business logic, so governance capabilities evolve independently of application code.
This architecture provides:
No code changes required. Existing business logic, configurations, and container images remain unchanged.
The following figure shows the end-to-end traffic governance workflow.
Capabilities
End-to-end canary release
Route specific traffic -- RPC requests, HTTP requests, and asynchronous messages -- through a complete call chain, from frontend gateways to backend microservices. Create lane groups and lanes to isolate traffic for different application versions, enabling safe, incremental rollouts.
For details, see End-to-end canary release and Implement an end-to-end canary release based on MSE Ingress gateways.
Graceful start and shutdown
Prevent traffic loss during deployments:
Graceful start: Delayed registration and low-traffic prefetching warm up a new application version before it receives full traffic. See Graceful start and Configure graceful start.
Graceful shutdown: Adaptive wait and proactive notification drain in-flight requests before shutting down an old version. See Graceful shutdown and Configure graceful shutdown.
Traffic protection
Protect services when traffic spikes or downstream dependencies fail. Capabilities include traffic control, isolation control, hot parameter protection, and web protection:
Throttling -- Limit burst traffic to prevent service overload. See Scenarios of traffic protection rules and Create a throttling rule.
Circuit breaking and degradation -- Block calls to unstable methods when timeouts or exception rates exceed thresholds, preventing cascading failures. See Create a circuit breaking rule.
Isolation -- Isolate unstable resources to prevent failures from spreading across the system. See Create an isolation rule.
Intra-zone Provider First -- Preferentially route calls to service providers in the same data center. Additional load balancing methods beyond the default round-robin are also available. See Configure the Intra-zone Provider First feature.
Tag-based routing
Assign service providers to groups using tags, then route traffic to specific groups. This enables scenarios such as routing test traffic to a dedicated set of instances. See Configure tag-based routing.
Service query
Query deployed services to inspect service lists, call relationships, and metadata. See Query services.
Use cases
Scenario | How Microservices Governance helps |
Safe deployments | Configuration management, graceful start, graceful shutdown, and end-to-end canary release eliminate traffic loss and enable incremental rollouts during version changes. |
Development environment isolation | End-to-end canary release logically isolates multiple development and test environments without extra physical machines, reducing environment conflicts and costs. |
Production stability | Throttling, circuit breaking, and isolation protect services during traffic surges or downstream failures. |
Benefits
Benefit | Details |
Non-invasive integration | Works with Spring Cloud, Apache Dubbo, and non-Java applications (Gin, gRPC-Go) without modifying code, configurations, or images. |
Zero upgrade cost | Compatible with existing service governance. Feature upgrades and performance optimizations require no additional development. |
Open source compatible | Fully compatible with open source frameworks. Integrates seamlessly with Kubernetes. Enhanced for performance, observability, and ease of use. |
Lightweight | Add governance capabilities without changing the existing architecture. |
Production proven | Validated at scale within Alibaba Group, demonstrating measurable improvements in system stability and development efficiency. |
Limitations
Item | Constraint |
Supported frameworks | Spring Cloud Edgware and later, Dubbo 2.5.0 and later, Gin 1.8.0 to 1.10.0, gRPC-Go 1.44.0 to 1.65.1. For a full list, see Java frameworks supported by Microservices Governance. |
Deployment targets | Applications deployed in Container Service for Kubernetes (ACK) clusters, Elastic Compute Service (ECS) instances, or Serverless App Engine (SAE). |
JDK versions (Java) | JDK 1.8, 11, 17, and 21. |
Maximum interfaces per application | 1,600 |
Get started
Activate the trial edition for a 30-day free trial of all features. After the trial, activate the official edition and purchase resource plans to optimize costs.
For a hands-on walkthrough, see Get started with Microservices Governance in 15 minutes (for Java applications).