RateLimiterDynamo: Add key to skip querying ttl #278
Merged
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.
TLDR: Adds an option allowing users to skip the check for TTL settings when using the
RateLimiterDynamo
.When assessing this library for use in a serverless environment (in this case AWS Lambda), we noticed that there was a significant overhead every time we instantiated a new rate limiter (so every time a new lambda started). This was due to
RateLimiterDynamo
's behaviour which is to query the table to make sure that the TTL has been set up correctly.While this is useful behavior on a long-running server, it doesn't make much sense in a serverless environment - once we've validated that the TTL is indeed set up correctly it doesn't make sense to keep checking it again and again and again.
I propose a new option which disables this check, in much the same way that you can disable
RateLimiterDynamo
's built-in table-creation logic.