-
Notifications
You must be signed in to change notification settings - Fork 694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] [Rate Limit] Add rate limter at client side #520
Comments
I understand where you're coming from, but using an interceptor or not at the client side - will entirely be a decision by the client. So, if a client doesn't choose to add the rate limiter interceptor, the server is not protected anyway! |
Well there is a point in this. If you don't have control over backend, there is no way you can add rate limit there. Thus you might want to rate limit on your side e.g to reduce potential cost. Fair proposal. Help wanted, we would accept it against |
I see.. that makes sense. |
* Add unary and streaming client-side rate-limit interceptors (#520) * Replace interface{} with any in ratelimit_test.go
We already have rate limit interceptor at server side after #134. I'm considering to have one at client side to protect target service if server, since server may have no rate limit at all.
The text was updated successfully, but these errors were encountered: