ref(server): Apply rate limits per item in fast-path #618
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.
Note: This is based on #616 and #617. Only look at the last commit.
Introduces
EnvelopeLimiter
, a utility that applies rate limits to envelope items. It implements logic around acheck
function that can either be used to check cached rate limits or Redis. Thecheck
function is called with the following rules:Items violating the rate limit are removed from the envelope. This follows a set of rules:
This is only used in the fast-path and will be added to normalization in a follow-up PR.
Changelog (Features): Apply cached rate limits to attachments and sessions in the fast-path when parsing incoming requests. (#618)