Why worker threads matter in Node.js

Introduction

Worker threads let Node.js do many things at once without slowing down. They help run heavy tasks separately so your app stays fast and smooth.

When you have a big calculation that takes time and you don't want to freeze the app.

When you want to handle multiple tasks at the same time without waiting for one to finish.

When you need to keep the app responsive while doing background work.

When you want to use multiple CPU cores to speed up processing.

When you want to avoid blocking the main thread with heavy tasks.

Syntax

Node.js

import { Worker } from 'worker_threads';

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

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

worker.postMessage('start');

The Worker class creates a new thread running a separate file.

You communicate with the worker using postMessage and listen for messages with on('message').

Examples

This example sends a message to the worker and logs the reply.

Node.js

import { Worker } from 'worker_threads';

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

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

worker.postMessage('Hello Worker');

This example creates a worker from a string and converts messages to uppercase.

Node.js

import { Worker } from 'worker_threads';

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

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

worker.postMessage('hello');

Sample Program

This program calculates the 10th Fibonacci number in a worker thread. It keeps the main app free to do other things while the calculation runs.

Node.js

import { Worker } from 'worker_threads';

function runWorker() {
  return new Promise((resolve, reject) => {
    const worker = new Worker(`
      const { parentPort } = require('worker_threads');
      function fibonacci(n) {
        if (n <= 1) return n;
        return fibonacci(n - 1) + fibonacci(n - 2);
      }
      parentPort.on('message', (num) => {
        const result = fibonacci(num);
        parentPort.postMessage(result);
      });
    `, { eval: true });

    worker.on('message', resolve);
    worker.on('error', reject);
    worker.postMessage(10);
  });
}

(async () => {
  const result = await runWorker();
  console.log('Fibonacci of 10 is', result);
})();

Important Notes

Worker threads run in separate memory, so you must send data back and forth using messages.

Use worker threads for CPU-heavy tasks, not for simple I/O operations.

Remember to handle errors from workers to avoid crashes.

Summary

Worker threads help Node.js run heavy tasks without freezing the app.

They let you use multiple CPU cores by running code in parallel.

You communicate with workers using messages to keep your app responsive.

Practice

1. Why do worker threads matter in Node.js?

easy

A. They allow running heavy tasks without freezing the main app.

B. They replace the need for asynchronous programming.

C. They make the app use less memory.

D. They automatically fix bugs in the code.

Solution

1. Step 1: Understand the main thread limitation

   Node.js runs JavaScript on a single main thread, so heavy tasks can block it and freeze the app.

2. Step 2: Role of worker threads

   Worker threads run heavy tasks in parallel, keeping the main thread free and the app responsive.

3. Final Answer:

   They allow running heavy tasks without freezing the main app. -> Option A

4. Quick Check:

   Worker threads keep app responsive = B [OK]

Hint: Worker threads run heavy tasks separately to avoid freezing [OK]

Common Mistakes:

• Thinking worker threads replace async programming
• Believing worker threads reduce memory automatically
• Assuming worker threads fix bugs

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

easy

A. const worker = createWorker('./worker.js');

B. const worker = Worker.create('./worker.js');

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

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

Solution

1. Step 1: Recall the Worker class usage

   Node.js uses the Worker class from 'worker_threads' module to create worker threads.

2. Step 2: Correct syntax

   The correct syntax is creating a new Worker instance with the file path as argument.

3. Final Answer:

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

4. Quick Check:

   Use new Worker() to create worker thread = D [OK]

Hint: Use new Worker() with file path to create worker [OK]

Common Mistakes:

• Using Worker.create() which does not exist
• Using Thread instead of Worker
• Calling createWorker() which is not a Node.js method

3. What will the following code output?

const { Worker, isMainThread, parentPort } = require('worker_threads');

if (isMainThread) {
  const worker = new Worker(__filename);
  worker.on('message', msg => console.log('From worker:', msg));
  worker.postMessage('Hello');
} else {
  parentPort.on('message', msg => {
    parentPort.postMessage(msg + ' World');
  });
}

medium

A. SyntaxError due to missing import

B. From worker: Hello

C. From worker: Hello World

D. No output because message event is not handled

Solution

1. Step 1: Understand main vs worker thread

   The main thread creates a worker running the same file. It sends 'Hello' to the worker.

2. Step 2: Worker message handling

   The worker listens for messages, appends ' World' to the received message, and sends it back.

3. Final Answer:

   From worker: Hello World -> Option C

4. Quick Check:

   Worker appends ' World' and sends back = A [OK]

Hint: Worker adds ' World' to message and replies [OK]

Common Mistakes:

• Confusing main thread and worker thread roles
• Missing parentPort import causing errors
• Assuming no output without understanding message events

4. Identify the error in this worker thread code snippet:

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

const worker = new Worker('./worker.js');
worker.on('message', (msg) => console.log(msg));
worker.postMessage('Start');

medium

A. Worker file path must be absolute

B. Missing import of parentPort in worker.js

C. Cannot call postMessage on worker instance

D. Event listener 'message' should be 'onmessage'

Solution

1. Step 1: Check main thread code

   Main thread creates worker and sends message correctly.

2. Step 2: Common worker.js mistake

   Inside worker.js, parentPort must be imported to receive and send messages.

3. Final Answer:

   Missing import of parentPort in worker.js -> Option B

4. Quick Check:

   Worker needs parentPort import to communicate = C [OK]

Hint: Worker.js must import parentPort to handle messages [OK]

Common Mistakes:

• Thinking postMessage is invalid on worker instance
• Believing file path must be absolute always
• Using 'onmessage' instead of 'message' event

5. You want to perform CPU-heavy calculations in a Node.js app without blocking the main thread. Which approach best uses worker threads to achieve this?

hard

A. Create a worker thread for each calculation and communicate results via messages.

B. Run all calculations in the main thread using async/await.

C. Use setTimeout to delay calculations in the main thread.

D. Spawn child processes instead of worker threads for parallelism.

Solution

1. Step 1: Understand CPU-heavy task impact

   CPU-heavy tasks block the main thread if run there, freezing the app.

2. Step 2: Worker threads for parallelism

   Creating worker threads for each calculation runs them in parallel without blocking the main thread, communicating results via messages.

3. Step 3: Evaluate other options

   Async/await does not prevent blocking for CPU tasks; setTimeout only delays but does not parallelize; child processes are heavier and more complex than worker threads.

4. Final Answer:

   Create a worker thread for each calculation and communicate results via messages. -> Option A

5. Quick Check:

   Use worker threads for parallel CPU tasks = A [OK]

Hint: Use worker threads to run heavy tasks in parallel [OK]

Common Mistakes:

• Thinking async/await avoids CPU blocking
• Using setTimeout to fix blocking issues
• Confusing child processes with worker threads