NodeJS Scalibility Tips
summary
Shows a concrete workflow: benchmark a simple QR PNG server with autocannon (200 concurrency yields ~100 req/s, avg latency ~2s) then compare to a minimal hello world (≈53k req/s) to find headroom. Use clinic.js (doctor, flame, bubble) to locate hotspots (png rendering function ~27% of time). Scale by cluster module or worker threads/piscina for a 3–4× throughput gain on an 8‑core machine, or by functional decomposition (microservices) and partitioning (sharding). Emphasizes logs metrics traces and choosing one primary optimization goal.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 3:06Defining scalability
- 4:11Establish a baseline
- 9:30Finding bottlenecks with Clinic.js
- 13:21Define optimization goals
- 15:06Observe in production
- 18:39Scale your architecture
- 21:10Cloning with Node.js
- 27:28Functional decomposition
- 31:04Partitioning data
- 33:31Summary of tips
- 36:01Q&A session
related talks
53mMastering Node.js Performance
25mMy node.js process is on fire
01h 04mNode.js performance analytics and best practices
13mMy Node.js process is on fire
22mMulti-tiered Node.js architectures
23mDecomposition of the Main Thread in Node.js to increase throughput
26mObserving Node.js: Using Metrics to Improve your Application Performance
53mMastering Node.js Performance
