add rate limiter #38
Merged
add rate limiter #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TimDaub
reviewed
Aug 6, 2022
TimDaub
approved these changes
Aug 6, 2022
This was referenced Aug 6, 2022
thanks, i am glad to be able to contribute |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds rate-limiter for individual endpoints. We can specify the rate limit of each endpoint in
workerData.endpoints. Using the package limiter we ensure that the number of calls is less than the limit. In case of missing config for an endpoint the rate limit for it is ignored.This PR also introduces the option to specify timeout per endpoint. The timeout can be specified in the config (sample config) for an endpoint or it can be overridden in the message.
Note: I have used limiter 2.0.1 as there is a bug with the latest version which prevents it's usage in ESM modules. (See this issue)