feat(rate-limiter): implement fixed window rate limiting algorithm#185
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Warning Review limit reached
More reviews will be available in 25 minutes and 28 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
This pull request implements the Fixed Window rate-limiting algorithm.
The algorithm can be used through the centralized
createRateLimiterAPI or directly via the dedicatedcreateFixedWindowAlgorithmfunction. This provides a simple and efficient rate-limiting strategy based on a fixed time window, where requests are counted and reset when the configured window expires.Usage with
createRateLimiterDirect Usage
Features
createRateLimitercreateFixedWindowAlgorithm