fix: add Postgres-backed rate limiter for multi-worker deployments#222
Merged
Conversation
Store rate-limit attempts in a shared table when RATE_LIMIT_BACKEND=postgres so configured limits apply cluster-wide instead of per process.
Drop the legacy implementation left after merging trusted-proxy support so ruff F811 passes in CI.
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
1 participant
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.
Summary
RateLimitAttempttable andPostgresRateLimitWindowfor shared rate-limit stateRATE_LIMIT_BACKEND(memorydefault,postgresfor multi-worker).env.exampleand add Postgres integration testCloses #218
Test plan
uv run pytest tests/utils/test_rate_limit.py tests/routers/core/test_account.py -k rate_limituv run ty check .