What is the point of rate limiting the gRPC API? #7220
unbeaten69
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What is the point of rate limiting the gRPC API? I mean the
CallRateMeteringInterceptor
class etc. From what I understand that API is meant to be used privately/locally, but when integrating it I found the rate limiting to be an obstacle actually and I had to use artificial delay to avoid being rate limited. At the same time it seems to be non-negligible amount of code in the Bisq app to implement these limits.I would assume that anyone who writes integration code can be responsible enough to not overwhelm/kill his own node with too many requests.
Happy to hear what was the rationale which justified introducing it.
Beta Was this translation helpful? Give feedback.
All reactions