Add Fixed and Sliding Window RateLimiters + PartitionedRateLimiter.Create #68695
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.
Backport of #67677 and #68087 to release/7.0-preview4
Customer Impact
We added new APIs for Sliding Window and Fixed Window rate limiters as well as
PartitionedRateLimiter.Create
for the default experience of creating aPartitionedRateLimiter
.We would love to start getting customer feedback on these core APIs. As well as make the new Rate Limiting Middleware in ASP.NET Core that is shipping in preview4 easier to use, which the
PartitionedRateLimiter.Create
API helps with.Testing
There is a good base set of test cases that are common among all the rate limiter implementations. As well as a suite of new tests for the
PartitionedRateLimiter
.Risk
Low. These APIs are in their own new assembly and shipped as standalone packages today. No other area in Runtime currently use them and the APIs used by ASP.NET Core were not modified.