Implement API rate limiting per user - #105
Closed
kael-developer[bot] wants to merge 1 commit into
Closed
Conversation
Implemented by Kael AI Agent
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.
Why
Problem
The FastAPI REST endpoints have no protection against misuse or accidental overload, risking denial‑of‑service for legitimate users, especially under heavy scheduling or batch operations.
Solution
Integrate a rate‑limiting middleware (e.g.,
slowapiorstarlette-rate-limit) that enforces configurable request quotas per authenticated user/IP. Provide defaults (e.g., 100 requests/minute) and allow admin override via config.Value
Prevents API abuse, ensures fair resource usage, and improves stability under load. Measurable by reduced 5xx error spikes during peak usage.
What changed
Implementation complete.
Closes #102
🤖 Implemented automatically by Kael AI Agent