Load Management in Node.js
summary
Explains how to protect a Node.js application from overload by using a rate limiter, a request queue, and traffic burst protection. Covers why each (rate limiting, queuing, burst protection) is needed and practical pitfalls when implementing them.
AI-written summary · about
chapters (13)
- 0:00Load management intro
- 2:18Basic app with monitoring
- 7:25Performance issues first incidents
- 8:50Client request throttling
- 13:03Scaling and state sync
- 17:27Queues to smooth load
- 20:58Burst Detector for traffic spikes
- 24:06Throttle service separation
- 26:44Event Loop blocking fixes
- 32:54Stale requests optimization
- 36:10Server state regional balancing
- 40:02Load testing with real logs
- 42:53Summary load tips
related talks
50mRate Limiting in Node js applications
33mNodeJS in a HighLoad Project
38mScaling NodeJS
30mDo Not Thrash the Node.js Event Loop
45mAsk the Maintainer: Nodejs
39mDon’t Let Node Blow Up on You
27mScaling NodeJS beyond the ordinary
22mBack pressure, or, how to not accept it if you can't handle it right now