Microservices Engine (MSE) Microservices Governance provides traffic monitoring and throttling capabilities that help you manage network traffic to ensure service availability and security.
Create a throttling rule
A throttling rule monitors the queries per second (QPS) of an application or service and immediately blocks traffic when the QPS reaches a threshold that you specify. This prevents application breakdowns caused by traffic surges. For more information, see Create a throttling rule.
Create an isolation rule
An isolation rule controls the number of concurrent threads for interfaces or dependencies to ensure system stability and reliability. For more information, see Configure isolation rules.
Create a circuit breaking rule
Circuit breaking rules prevent system failures caused by inter-service calls. When a service fails or responds slowly, a circuit breaking rule stops requests to that service to maintain overall application stability. For more information, see Configure circuit breaking rules.
Create a hot parameter throttling rule
Hot parameter throttling rules allow you to throttle RPC requests and HTTP requests based on the request type. For more information, see Create a hot parameter throttling rule for RPC requests or custom interface requests and Configure hot spot parameter protection rules (HTTP requests).
Configure tag-based routing
Tag-based routing lets you tag traffic or machines so that traffic matching specific characteristics is routed to designated nodes. For more information, see Configure tag-based routing.
Configure a canary release for messaging
MSE supports canary releases for RocketMQ messages, applicable to scenarios such as canary releases, end-to-end canary releases, and development environment isolation. For more information, see Configure message canary release.