You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by "flycash (GitHub)" <gi...@apache.org> on 2020/03/18 14:26:55 UTC

[GitHub] [dubbo-go] flycash opened issue #431: Enhancement: Rule based implementation of rate limit.

<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:

The implementation of rate limit strategy based on rules.
In this implementation, we allow user defines rules when to reject the new quest.

For example, user could define rule "cpu>90" which means that dubbogo should reject the new request if the cpu usage rate is greater than 90%.

The targets:
1. Allow user defines different rule and enable boolean operator, like "cpu > 90 || io>30"
2. The rules could be stored in config center, file system... 

**Why is this needed**:

Even though we have several rate limit strategies, all of them are "static" strategies. They don't make the decision based on the server's current status.

[ Full content available at: https://github.com/apache/dubbo-go/issues/431 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org