Implement API Rate Limiting & Throttling - #39
Merged
akargi merged 1 commit intoAug 21, 2026
Conversation
Implement API Rate Limiting & Throttling
11 tasks
This file contains hidden or 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
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.
PR Description — Implement API Rate Limiting & Throttling
Summary
This PR implements comprehensive API rate limiting and throttling to protect the service from abuse, improve resource allocation, and maintain system stability under high traffic. The implementation supports tier-based, endpoint-based, and IP-based limits with Redis-backed distributed state management.
Changes
Added NestJS rate-limiting guard/middleware.
Implemented sliding-window rate limiting.
Added Redis-backed rate-limit state management for distributed environments.
Added tier-based quotas:
Added configurable per-endpoint rate limits.
Added IP-based throttling for unauthenticated requests.
Added
X-RateLimit-*response headers for rate-limit visibility.Added
429 Too Many Requestsresponses withRetry-Afterheaders when limits are exceeded.Added configurable admin controls for runtime rate-limit adjustments.
Added bypass support for critical system operations.
Added graceful handling of rate-limit failures and high-load scenarios.
Testing
429responses.Closes #28