workflow:api-rate-limiting-tuning
API Rate Limiting Tuning overview
Tunes API rate-limiting configurations to balance abuse prevention with legitimate traffic needs -- analyzing request-rate distributions across API consumers to identify percentile thresholds, reviewing 429-response incidence and correlating with customer-impact tickets, evaluating burst-allowance and sliding-window parameters against traffic-spike patterns, load-testing proposed rate-limit changes in staging with synthetic client profiles, configuring per-endpoint and per-tier differentiated limits, updating rate-limit response headers and developer documentation, and monitoring post-deployment metrics for false-positive throttling. Produces rate-limit configuration change record and impact analysis. Excludes API architecture redesign.
Attributes
Outgoing edges
- domain:web-development·DomainWeb Development
- domain:platform-engineering·DomainPlatform Engineering
- role:staff-engineer·RoleStaff Engineer
- role:platform-engineer·Role
- org-unit:platform-team·OrgUnitPlatform Team
- org-unit:engineering·OrgUnitEngineering
- skill-area:rate-limiting·SkillAreaRate Limiting
- skill-area:web-performance·SkillAreaWeb Performance Engineering
- responsibility:performance-budget-tracking·ResponsibilityPerformance budget tracking
- responsibility:slo-definition·ResponsibilitySLO definition
Incoming edges
- stack-profile:rate-limiting-api-throttle·StackProfileRate Limiting / API Throttle (Go, Redis, Prometheus, Docker)