Scaling Strategy
On this page
Vertical vs Horizontal Scaling
Vertical scaling increases resources (CPU, memory) for a single instance. Horizontal scaling adds more instances behind a load balancer.
Layered Scaling Strategy
- Optimize event loop usage
- Add clustering for multi-core usage
- Scale instances horizontally
- Introduce caching (CDN, in-memory, Redis)
- Shard databases if necessary
Stateless Services
Horizontal scaling requires stateless design. Sessions and caches must use shared external storage.
Production Guidance
Scale based on measured bottlenecks. Do not prematurely introduce complex distributed systems without evidence of need.
Resilience Consideration
Scaling is not only about throughput. It is also about fault tolerance and graceful degradation under partial outages.