NODE.JS GUIDE
Node.js Clustering Explained for Interviews
By the HireReadyAI team · 8 min read
When to use cluster, how workers share a port, and how this differs from containers and worker threads.
Why cluster
A single Node process uses one main JavaScript thread. On multi-core machines, the cluster module (or an equivalent process manager) runs multiple workers behind a shared port so CPU-bound request handling can use more cores. Clustering helps throughput for many concurrent connections; it does not make one synchronous CPU task faster inside a single request unless you also change that work.
How cluster works
A primary process forks workers. Incoming connections are distributed to workers. Each worker is a separate process with its own memory. Shared state must live externally — Redis, a database, or another service — not in a process-local variable if you need consistency across workers.
Cluster vs containers vs worker threads
In Kubernetes you often run multiple pods instead of Node’s cluster module. Worker threads share memory within a process and suit CPU tasks you want to offload without a full process boundary. Choose based on deployment model and isolation needs.
Pitfalls
- In-memory sessions break across workers without sticky sessions or external stores
- Too many workers can thrash CPU and multiply DB connections
- Unhandled crashes need respawn strategy and health checks