Scaling strategy helper
Five questions about what's actually slow — one primary recommendation, what it costs in complexity, and what not to do.
Recommended strategy
Why
Complexity cost
What not to do
Also consider
About this tool
Most scaling advice starts with the solution ("just add Kubernetes") instead of the problem. This tool works the other way: it asks what's actually slow, and picks one strategy — because doing one right thing beats doing three fashionable ones.
The rules are deterministic and deliberately conservative: measure first, cache before you scale, vertical before horizontal, and never add instances to fix a slow query. Everything runs in your browser.
Read more
- HTTP Caching — the caching layer you already have
- What is a CDN — offload static assets to the edge
- Nginx reverse proxy for multiple Node.js apps — the building block of load balancing
- How to use pm2 to serve a Node.js app — run multiple processes on one box
- What's the best platform to deploy your projects? — when a PaaS does the scaling for you
Free books, courses, and software
Get my programming books, course editions, and complete software.
Get the download library →