Rate Limiting in Node js applications
summary
Shows runnable demos at rate-limits.dev and explains concrete choices: GitHub’s odd 5,000 requests per hour fixed-window policy, a client-side implementation used to avoid hitting GitHub, and a released tool for automating releases. Compares algorithms with implementation costs and numbers — fixed and sliding windows vs token-bucket (stores two integers, e.g. one token every 2s, allows bursts) and exponential delay for login attempts — and gives code patterns and deployment advice.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:10Why Rate Limiting
- 1:42Mitigation
- 3:56Fixed Window
- 4:17Fixed Blocks
- 7:00Request Count
- 8:20Fixed Window Rate Limiting
- 10:18Fixed Window Pros and Cons
- 12:30Continuous Window
- 15:37Sliding Window Code
- 19:02Bucket Rate Limiting
- 23:26Bucket Rate Limiting Implementation
- 26:45Pros and Cons
- 29:11Exponential Delay
- 35:59Launch ins
- 37:35Recommendations
- 42:08RateLimit
- 46:35Authentication Rate Limiting
related talks
44mLoad Management in Node.js
15mNot Your Regular Rate Limiting
41mHigh Volume Ratelimiting with Redis
25mArt and Science of Rate Limits for APIs
42mThe Node.js Highway: Attacks Are At Full Throttle
09mNot Your Regular Rate Limiting GraphQL
26mTraffic Management w. Rate Limiting to Ensure API Scalability & Resiliency
46mNodeJS Scalibility Tips