Microservices Governance enhances mainstream open source microservices frameworks, such as Spring Cloud and Apache Dubbo, without modifying your applications. Microservices Governance provides comprehensive service governance and traffic protection capabilities and decouples middleware from your business.
If you do not activate Microservices Governance, you can activate the trial edition of Microservices Governance for a 30-day free trial of all features. After the trial period ends, you can activate the official edition and purchase resource plans to reduce costs.
Capabilities and scenarios of Microservices Governance
End-to-end traffic governance
MSE Microservices Governance provides a complete set of governance solutions for microservices to help enterprises quickly build a complete and robust microservices system. The following figure shows the workflow of the end-to-end traffic governance process that is implemented by Microservices Governance.
Implement agile development of microservices at low costs
Microservices Governance allows you to logically isolate multiple development environments from each other, without generating extra costs for adding physical machines. This helps resolve environment preemption and conflict issues and implement agile development.
Development environment isolation: Microservices Governance provides the end-to-end canary release feature to isolate development environments. This allows you to add multiple development and test environments without generating extra costs and implement agile development.
Eliminate risks during application version changes
Microservices Governance provides features to eliminate the risks that may occur during application version changes. The features include configuration management, graceful start, graceful shutdown, and end-to-end canary release.
Graceful start
The delayed registration and low-traffic prefetching capabilities provided by the graceful start feature can effectively prevent traffic loss when a new application version is released. For more information, see Graceful start.
Graceful shutdown
The adaptive wait and proactive notification capabilities provided by the graceful shutdown feature can effectively prevent traffic loss when an old application version is disabled. For more information, see Graceful shutdown.
End-to-end canary release
If you enable end-to-end canary release, you can create lane groups and lanes to accurately control various types of traffic, such as remote procedure call (RPC) requests, HTTP requests, and asynchronous messages. This helps implement traffic governance for applications in lanes from frontend and gateways to backend microservices, and accelerates the end-to-end canary release process in the microservices architecture. For more information, see End-to-end canary release.
Improve stability during business operations
Microservices Governance provides capabilities to effectively perform traffic control, load balancing, fault isolation, and degradation when traffic surges or related services fail in specific scenarios. The capabilities include throttling, degradation, circuit breaking, and isolation.
Throttling: Microservices Governance provides the throttling feature to throttle burst traffic. This allows the system to process a large number of requests without service interruptions. For more information, see Scenarios of traffic protection rules.
Circuit breaking and degradation: If a method is unstable, issues such as timeouts or increases in exception percentages may occur. In this case, calls to the method are not allowed. This results in request failures in a short period of time and prevents errors from affecting the stability of the entire workflow. For more information, see Create a circuit breaking rule.
Intra-zone provider first: When an application calls a service, the service providers in the same data center are preferentially called. This allows traffic to be forwarded in the same zone. In addition to the default polling method, you can use other methods to implement load balancing. For more information, see Configure the Intra-zone Provider First feature.
Benefits
Seamless access: You can enable Microservices Governance for microservice applications such as Spring Cloud applications, Dubbo applications, and non-Java applications without modifying application code, configurations, and images. This ensures business continuity and stability.
Zero upgrade costs: Microservices Governance is compatible with existing service governance methods. You can upgrade features and optimize performance without the need for additional development workloads.
Full compatibility with open source products: Microservices Governance is fully compatible with open source products and is seamlessly interconnected with Kubernetes. Microservices Governance is also enhanced in terms of performance , observability, and convenience.
Lightweight: You can use efficient microservices governance capabilities without the need to change the existing business architecture.
Large-scale production practices: The verification of large-scale production practices within Alibaba Group indicates that Microservices Governance can significantly improve system stability and development efficiency and ensure normal business operations.
Features
Feature module | Description | References |
Service query | This feature allows you to query the service list and service details of deployed applications, including the basic service information, service call relationships, and metadata. | |
Graceful start and shutdown |
| |
Tag-based routing | This feature allows you to allocate one or more service providers to the same group by using tags. This way, you can forward traffic to service providers in specific groups. | |
End-to-end canary release | This feature allows you to create lane rules to add one or more applications of the same version to the same lane. This way, traffic is forwarded in the specified lane and end-to-end traffic isolation is implemented. | |
Traffic protection | This feature ensures service stability in multiple aspects, such as traffic control, isolation control, hot parameter protection, and web protection. This feature provides professional and stable traffic protection methods and second-level traffic usage distribution analysis. |
Limits
Item | Requirement |
Microservices frameworks |
For more information about supported components, see Java frameworks supported by Microservices Governance. |
Access methods | Applications deployed in Container Service for Kubernetes (ACK) clusters, Elastic Compute Service (ECS) instances, or Serverless App Engine (SAE) are supported. |
Java Development Kit (JDK) versions of Java applications | JDK 1.8, 11, 17, and 21. |
Maximum number of access resources (interfaces) | Maximum number of access resources (interfaces) for an application: 1,600. |
Get started with Microservices Governance
For more information about how to enable Microservices Governance for Java applications, see Get started with Microservices Governance in 15 minutes (for Java applications).
References
For the regions supported by Microservices Governance, see Supported regions.
For information about the billable items, billing methods, billing cycles, billing formulas, and pricing of MSE Microservices Governance, see Billing overview of Microservices Governance.