Microservices Governance enhances mainstream open source frameworks like Spring Cloud and Apache Dubbo without code changes. The service provides a rich set of governance and traffic protection features, decoupling middleware from business logic.
If you have not yet activated Microservices Governance, you can enable the trial edition for a 30-day, full-featured trial. After the trial period, you can upgrade to the official edition and purchase resource plans to receive discounts.
Capabilities and use cases
End-to-end traffic governance
MSE Microservices Governance provides a comprehensive governance solution for all aspects of your microservices architecture, helping you quickly build a complete and resilient system.
Low-cost agile microservices development
Use development environment isolation to create multiple, logically isolated development environments without increasing hardware costs. This approach resolves resource contention and conflicts, enabling agile development.
Development environment isolation uses end-to-end canary release for logical isolation, allowing you to create multiple development and testing environments without increasing costs.
Mitigate risks during changes
Eliminate risks during application changes by using configuration management, graceful start and shutdown, and end-to-end canary releases.
Graceful start
Delayed registration and low-traffic warm-up during a graceful start prevent traffic loss when new application versions are launched. For more information, see Graceful start.
Graceful shutdown
Adaptive waiting and proactive notifications during a graceful shutdown prevent traffic loss when old application versions are taken offline. For more information, see Graceful shutdown.
End-to-end canary release
Create lane groups and lanes to precisely control various traffic types, including RPC, HTTP, and asynchronous messages. This ensures that traffic is contained within a specific lane from the front end, through the gateway, to all backend microservices. This capability allows you to quickly implement end-to-end canary releases in your microservices architecture. For more information, see End-to-end canary release.
Enhance service stability
Use features like throttling, circuit breaking and degradation, and isolation to protect your services against unexpected traffic spikes or dependency failures. These capabilities help you manage traffic, smooth bursts, isolate faults, and degrade services gracefully.
Throttling: This feature limits sudden traffic bursts, ensuring your service remains stable while handling as many requests as possible. For more information, see Scenarios for traffic protection rules.
Circuit breaking and degradation: When a method becomes unstable, for example, due to increased latency or a high error rate, this feature limits calls to that method, allowing it to fail fast. This prevents the issue from affecting the stability of the entire call chain. For more information, see Create a circuit breaking rule.
Intra-zone Provider First: When an application calls a service, it prioritizes providers in the same availability zone. This keeps traffic within a single zone and supports load balancing methods beyond the default round-robin approach. For more information, see Configure Intra-zone Provider First.
Benefits
Non-invasive integration: Connect your applications to the governance center without changing their code, configuration, or images. Microservices Governance supports Spring Cloud, Dubbo, and multi-language applications, ensuring business continuity and stability.
Zero upgrade cost: The service is compatible with existing service governance methods. You can upgrade features and optimize performance without additional development.
Fully compatible with open source: The service is 100% compatible with open source products and integrates seamlessly with Kubernetes. It also provides enhanced performance, observability, and usability.
Lightweight: You can access efficient microservices governance capabilities without altering your existing business architecture.
Production-proven at scale: Proven in large-scale production at Alibaba Group, the service improves system stability and development efficiency, ensuring smooth business operations.
Features
Feature | Description | Related documentation |
Service query | Query lists and details of deployed services, including basic information, service call relationships, and their metadata. | |
Graceful start and shutdown |
| |
Tag-based routing | Use tags to group providers of one or more services. This constrains traffic to flow only within the specified group, achieving traffic isolation. | |
End-to-end canary release | Create lane rules to group identical versions of one or more applications into the same lane. This constrains traffic to flow only within the specified lane, achieving end-to-end traffic isolation. | |
Traffic protection | Traffic protection ensures business stability by providing professional, reliable traffic protection and per-second analysis of traffic distribution. Protection is available across multiple dimensions, including throttling, isolation, hot parameter protection, and web protection. |
Limitations
Item | Constraint |
Microservice frameworks |
For more information about supported components, see Java frameworks supported by Microservices Governance. |
Deployment targets | Supports applications running on Container Service for Kubernetes (ACK), Elastic Compute Service (ECS), and Serverless App Engine (SAE). |
JDK versions for Java applications | Supports applications that use JDK 1.8, 11, 17, or 21. |
Number of connected resources (interfaces) | Each application supports a maximum of 1,600 connected resources (interfaces). |
Get started
To learn how to integrate Microservices Governance with a Java application, see 15-minute quickstart for Microservices Governance (Java).
More information
For information about the regions where Microservices Governance is available, see Supported regions for Microservices Governance.
For details on the billable items, billing methods, billing cycles, billing formulas, and pricing for Microservices Governance, see Billing overview for Microservices Governance.