Not Your Regular Rate Limiting
summary
GraphQL rate limiting uses query cost analysis rather than request counts, assigning weights to types and resolves so limits match actual backend work. Examples: Shopify gives mutations = 10 points and per-type points, GitHub performs static/dynamic/response cost analysis (static counts nodes to block deep queries, dynamic measures cost during execution but may already perform reads, response charges after the fact), Yelp weights returned types, Apollo compiler in Rust adds recursion limits, and ML models can predict costs.
AI-written summary · about
chapters (9)
- 0:00Introduction to rate limits
- 1:06Why rate limiting matters
- 2:25GraphQL-specific challenges
- 3:58Query cost analysis methods
- 6:35Dynamic and response analysis
- 8:16Implementation considerations
- 9:25Real-world examples
- 11:01Future trends in rate limiting
- 12:57Conclusion and resources
related talks
09mNot Your Regular Rate Limiting GraphQL
24mUnderstanding GraphQL Security: Protecting Your Server from Abuse
26mWhen GraphQL Gets Expensive: Performance & Cost Patterns in Production Serverless Architectures
50mRate Limiting in Node js applications
51mGraphQL: advantages, challenges, and how to overcome them
31mLessons from Scaling GraphQL to Half a Billion Requests per Minute
30mBeyond REST: GraphQL API Management
27mDesigning Secure GraphQL APIs : Not a Paradigm Shift but Handling Complexity