Setup Rate Limiting
Implement comprehensive API rate limiting with advanced control mechanisms: $ARGUMENTS
Current API State
- Framework detection: @package.json or @requirements.txt (Express, FastAPI, Spring Boot, etc.)
- Existing rate limiting: !
grep -r "rate.limit\|throttle\|rateLimit" src/ 2>/dev/null | wc -l
- Redis availability: !
redis-cli ping 2>/dev/null || echo "Redis not available"
- API endpoints: !
grep -r "route\|endpoint\|@app\\.route" src/ 2>/dev/null | wc -l
Task
Implement production-ready rate limiting system with sophisticated algorithms and user policies:
Rate Limit Type: Use $ARGUMENTS to focus on API rate limiting, authentication limiting, file upload controls, or database access limiting
Rate Limiting Architecture:
- Algorithm Implementation - Token bucket, sliding window, fixed window, leaky bucket algorithms
- User Policies - Tier-based limits, authenticated vs anonymous, user-specific quotas, IP-based controls
- Storage Backend - Redis integration, distributed rate limiting, persistence strategies, failover mechanisms
- Endpoint Configuration - Per-route limits, method-specific rules, dynamic configuration, A/B testing
- Monitoring & Analytics - Usage tracking, abuse detection, performance metrics, alerting systems
- Bypass Mechanisms - Whitelist management, internal request handling, emergency overrides
Advanced Features: Adaptive rate limiting, geo-based controls, API key management, quota systems, abuse prevention.
Production Readiness: High availability, performance optimization, security controls, comprehensive monitoring.
Output: Complete rate limiting system with intelligent policies, comprehensive monitoring, and advanced abuse prevention capabilities.
1---2name: setup-rate-limiting3description: Implement comprehensive API rate limiting with advanced control mechanisms: $ARGUMENTS4---56# Setup Rate Limiting78Implement comprehensive API rate limiting with advanced control mechanisms: **$ARGUMENTS**910## Current API State1112- Framework detection: @package.json or @requirements.txt (Express, FastAPI, Spring Boot, etc.)13- Existing rate limiting: !`grep -r "rate.limit\|throttle\|rateLimit" src/ 2>/dev/null | wc -l`14- Redis availability: !`redis-cli ping 2>/dev/null || echo "Redis not available"`15- API endpoints: !`grep -r "route\|endpoint\|@app\\.route" src/ 2>/dev/null | wc -l`1617## Task1819Implement production-ready rate limiting system with sophisticated algorithms and user policies:2021**Rate Limit Type**: Use $ARGUMENTS to focus on API rate limiting, authentication limiting, file upload controls, or database access limiting2223**Rate Limiting Architecture**:241. **Algorithm Implementation** - Token bucket, sliding window, fixed window, leaky bucket algorithms252. **User Policies** - Tier-based limits, authenticated vs anonymous, user-specific quotas, IP-based controls263. **Storage Backend** - Redis integration, distributed rate limiting, persistence strategies, failover mechanisms274. **Endpoint Configuration** - Per-route limits, method-specific rules, dynamic configuration, A/B testing285. **Monitoring & Analytics** - Usage tracking, abuse detection, performance metrics, alerting systems296. **Bypass Mechanisms** - Whitelist management, internal request handling, emergency overrides3031**Advanced Features**: Adaptive rate limiting, geo-based controls, API key management, quota systems, abuse prevention.3233**Production Readiness**: High availability, performance optimization, security controls, comprehensive monitoring.3435**Output**: Complete rate limiting system with intelligent policies, comprehensive monitoring, and advanced abuse prevention capabilities.
tools-only