When to use workers vs cluster in Node.js

Introduction

Workers and clusters help Node.js run multiple tasks at the same time to make programs faster and more efficient.

Use workers when you want to run heavy calculations or tasks in the background without stopping the main program.

Use cluster when you want to handle many web requests at once by using multiple CPU cores.

Use workers to split a big job into smaller parts that run separately and then combine results.

Use cluster to improve the performance of a web server by creating copies of the server process.

Use workers when you need to run tasks that do not share memory but can communicate by messages.

Syntax

Node.js

const { Worker } = require('worker_threads');

const worker = new Worker('./worker.js');

worker.on('message', (msg) => {
  console.log('Message from worker:', msg);
});

worker.postMessage('start');

Workers run in separate threads and communicate by sending messages.

Clusters create multiple Node.js processes that share the same server port.

Examples

This cluster example creates one worker per CPU core to handle HTTP requests.

Node.js

const cluster = require('cluster');
const http = require('http');
const numCPUs = require('os').cpus().length;

if (cluster.isPrimary) {
  for (let i = 0; i < numCPUs; i++) {
    cluster.fork();
  }
} else {
  http.createServer((req, res) => {
    res.writeHead(200);
    res.end('Hello from worker ' + process.pid);
  }).listen(8000);
}

This worker example runs a small task that processes a message and sends back a result.

Node.js

const { Worker } = require('worker_threads');

const worker = new Worker(`
  const { parentPort } = require('worker_threads');
  parentPort.on('message', (msg) => {
    parentPort.postMessage(msg + ' processed');
  });
`, { eval: true });

worker.on('message', (msg) => console.log(msg));
worker.postMessage('data');

Sample Program

This program uses cluster to create one worker per CPU core. Each worker runs a simple HTTP server that responds with its process ID. The primary process manages workers and logs when they start or stop.

Node.js

const cluster = require('cluster');
const http = require('http');
const numCPUs = require('os').cpus().length;

if (cluster.isPrimary) {
  console.log(`Primary ${process.pid} is running`);

  for (let i = 0; i < numCPUs; i++) {
    cluster.fork();
  }

  cluster.on('exit', (worker, code, signal) => {
    console.log(`Worker ${worker.process.pid} died`);
  });
} else {
  http.createServer((req, res) => {
    res.writeHead(200);
    res.end(`Hello from worker ${process.pid}`);
  }).listen(8000);

  console.log(`Worker ${process.pid} started`);
}

Important Notes

Workers are best for CPU-heavy tasks that can run independently.

Clusters are best for scaling network servers to use all CPU cores.

Workers communicate by passing messages; clusters share server ports but run separate processes.

Summary

Workers run code in separate threads for background tasks.

Clusters run multiple processes to handle many requests.

Choose workers for heavy computation and clusters for scaling servers.

Practice

1. What is the main reason to use worker_threads in Node.js instead of cluster?

easy

A. To restart crashed processes automatically

B. To create multiple server instances for load balancing

C. To share the same server port across processes

D. To run CPU-heavy tasks without blocking the main thread

Solution

1. Step 1: Understand worker_threads purpose

   Workers run code in separate threads to handle CPU-intensive tasks without blocking the main event loop.

2. Step 2: Compare with cluster usage

   Clusters create multiple processes to handle many incoming requests and improve server scalability, not for CPU-heavy tasks.

3. Final Answer:

   To run CPU-heavy tasks without blocking the main thread -> Option D

4. Quick Check:

   Workers = CPU tasks [OK]

Hint: Workers handle CPU tasks; clusters handle many requests [OK]

Common Mistakes:

• Confusing workers with clusters for load balancing
• Thinking clusters run in threads instead of processes
• Assuming workers share server ports automatically

2. Which of the following is the correct way to create a worker thread in Node.js?

easy

A. const worker = new Worker('worker.js');

B. const worker = cluster.fork('worker.js');

C. const worker = new Thread('worker.js');

D. const worker = new WorkerThread('worker.js');

Solution

1. Step 1: Recall worker_threads syntax

   The correct syntax to create a worker thread is using the Worker class from 'worker_threads' module: new Worker('filename').

2. Step 2: Identify incorrect options

   const worker = cluster.fork('worker.js'); uses cluster.fork which is for clusters, not workers. Options C and D use incorrect class names.

3. Final Answer:

   const worker = new Worker('worker.js'); -> Option A

4. Quick Check:

   Worker class = new Worker() [OK]

Hint: Use new Worker() from 'worker_threads' module [OK]

Common Mistakes:

• Using cluster.fork() to create workers
• Using wrong class names like Thread or WorkerThread
• Forgetting to import Worker from 'worker_threads'

3. Consider this Node.js code snippet using cluster:

const cluster = require('cluster');
if (cluster.isPrimary) {
  cluster.fork();
  cluster.fork();
} else {
  console.log('Worker process started');
}

What will be the output when you run this code?

medium

A. No output

B. Worker process started

C. Worker process started
Worker process started

D. SyntaxError

Solution

1. Step 1: Understand cluster.fork behavior

   cluster.fork() creates a new worker process that runs the same script but with cluster.isPrimary false.

2. Step 2: Count worker processes and output

   Two cluster.fork() calls create two workers, each printing 'Worker process started'. So output appears twice.

3. Final Answer:

   Worker process started Worker process started -> Option C

4. Quick Check:

   Two forks = two outputs [OK]

Hint: Each fork runs worker code once [OK]

Common Mistakes:

• Thinking only one worker runs
• Expecting output from primary process
• Confusing cluster.isPrimary with cluster.isWorker

4. This code tries to use workers but has an error:

const { Worker } = require('worker_threads');
const worker = new Worker('./worker.js');
worker.on('message', (msg) => console.log(msg));
worker.postMessage('start');

What is the likely problem here?

medium

A. The worker script must use parentPort to receive messages

B. You cannot send messages to workers using postMessage

C. Worker constructor requires a function, not a file path

D. Missing cluster module import

Solution

1. Step 1: Check worker communication setup

   Workers communicate via message passing. The worker script must listen on parentPort to receive messages.

2. Step 2: Identify missing code in worker.js

   If worker.js does not use parentPort.on('message'), it cannot handle messages sent by postMessage, causing no response or error.

3. Final Answer:

   The worker script must use parentPort to receive messages -> Option A

4. Quick Check:

   Worker script needs parentPort listener [OK]

Hint: Worker script must listen on parentPort for messages [OK]

Common Mistakes:

• Thinking postMessage is invalid for workers
• Confusing worker_threads with cluster usage
• Assuming Worker constructor takes a function directly

5. You have a Node.js server that handles many HTTP requests and also performs heavy image processing. How should you design your app using workers and cluster for best performance?

hard

A. Use only workers to run multiple server instances and process images

B. Use cluster to run multiple server processes and workers inside each process for image processing

C. Use only cluster to handle requests and do image processing in the main thread

D. Use a single process with no workers or cluster for simplicity

Solution

1. Step 1: Understand cluster for scaling servers

   Cluster creates multiple processes to handle many HTTP requests efficiently by using multiple CPU cores.

2. Step 2: Use workers for CPU-heavy tasks

   Heavy image processing should run in worker threads to avoid blocking the event loop in each server process.

3. Step 3: Combine cluster and workers

   Run cluster to scale server processes, and inside each process, use workers for heavy computation tasks.

4. Final Answer:

   Use cluster to run multiple server processes and workers inside each process for image processing -> Option B

5. Quick Check:

   Cluster for scaling + workers for CPU tasks [OK]

Hint: Cluster scales servers; workers handle heavy tasks inside each process [OK]

Common Mistakes:

• Doing heavy tasks in main thread blocking requests
• Using only workers without clustering for many requests
• Ignoring multi-core CPU benefits