Sentinel Rate Limiting and Downgrade

Traffic Based on Sentinel

Dubbo-go provides a built-in rate limiting component, allowing users to adjust rate limiting values and post-limiting behaviors according to their business scenarios. The specifics can be defined and implemented in TpsLimiter. Users can set a simple rate limiting strategy on the server side in a manner similar to the following:

  1. server.WithTpsLimiter("method-service") // Currently supports implementations like method-service, polaris, etc.
  2. server.WithTpsLimiterXxx() // Set rate limiting related thresholds, please fill in according to the specific method
  3. //tps.limit.strategy: "slidingWindow"
  4. //tps.limit.rejected.handler: "default"
  5. //tps.limit.interval: 1000
  6. //tps.limit.rate: 3

The built-in rate limiting strategy in Dubbo-go is relatively simple. For more complex scenarios, we recommend using professional third-party frameworks like Sentinel to achieve richer and more flexible rate limiting strategies.

You can view the complete source code for this example, and also refer to the Java example of Dubbo+Sentinel for more inspiration.

Provider Rate Limiting

QpS Based Rate Limiting

Rate Limiting Based on Concurrent Task Count (Current Running Task Count)

Consumer Rate Limiting

Circuit Breaker Strategy

Rate Limiting Based on Concurrent Request Count (Requests Awaiting Response)

Feedback

Was this page helpful?

Yes No

Last modified September 30, 2024: Update & Translate Overview Docs (#3040) (d37ebceaea7)