feat: add Redis-backed shared rate limiting with in-memory fallback - #477
Merged
Nsanjayboruds merged 1 commit intoJul 19, 2026
Merged
Conversation
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.
Description
Fixes #463
Implemented Redis-backed shared rate limiting with a graceful in-memory fallback.
The application previously relied on express-rate-limit's default in-memory store, which caused rate limit counters to reset after server restarts and prevented consistent enforcement across multiple server instances.
This change adds optional Redis support while keeping local development behavior unchanged.
Changes Made
rate-limit-rediswhenREDIS_URLis configured.globalIpLimiterauthIpLimiterotpIpLimiterbotIpLimiteruserRateLimiteradminRateLimiterREDIS_URLis not configuredREDIS_URLdocumentation in.env.example.Implementation Details
Testing Done
Verified locally with a real Upstash Redis instance:
REDIS_URL.Backward Compatibility
No breaking changes.
Local development continues working without requiring Redis configuration.
Related Issue
Closes #463