You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a service provider, I want to implement rate limiting on my REST API endpoints to ensure fair usage, prevent abuse, and help maintain the quality of service for all users.
Acceptance Criteria
The API enforces a limit of 100 requests per minute per user.
Upon reaching the limit, the API returns a 429 (Too Many Requests) HTTP status code.
Rate limiting headers such as X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset are included in the response.
Users are informed of the duration after which they can resume making requests once rate limited.
The system supports a mechanism to whitelist certain users or IPs from rate limiting.
The API provides endpoint-specific rate limits if necessary.
The rate limiting system is scalable and can handle an increase in traffic.
The implementation of rate limiting does not significantly impact the response time of the API.
sequenceDiagram
participant User
participant API
participant RateLimiter
User->>API: Request resources
API->>RateLimiter: Check user's request count
RateLimiter->>API: User under limit
API->>User: Provide requested resources
Note over User,API: User makes too many requests
RateLimiter-)API: User over limit
API->>User: Return 429 Too Many Requests
Loading
The text was updated successfully, but these errors were encountered:
Rate Limiting Specifications
As a service provider, I want to implement rate limiting on my REST API endpoints to ensure fair usage, prevent abuse, and help maintain the quality of service for all users.
Acceptance Criteria
X-RateLimit-Limit
,X-RateLimit-Remaining
, andX-RateLimit-Reset
are included in the response.The text was updated successfully, but these errors were encountered: