Creating worker threads in Node.js

Introduction

Worker threads let you run code in the background without stopping your main program. This helps your app stay fast and smooth.

When you have heavy calculations that might slow down your app.

When you want to do multiple tasks at the same time.

When you want to keep your app responsive while doing background work.

When you need to run code that takes a long time without freezing the user interface.

Syntax

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('start');

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

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

Examples

This starts a worker thread running the code in worker.js.

Node.js

import { Worker } from 'worker_threads';

// Create a worker from a file
const worker = new Worker('./worker.js');

This listens for messages sent from the worker thread.

Node.js

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

This sends a message to the worker thread.

Node.js

worker.postMessage('Hello Worker');

Sample Program

This example shows how to create a worker thread inside the same file. The main thread sends a message to the worker, and the worker replies back.

Node.js

import { Worker, isMainThread, parentPort } from 'worker_threads';

if (isMainThread) {
  // This is the main thread
  const worker = new Worker(new URL(import.meta.url));

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

  worker.postMessage('Hello Worker');
} else {
  // This is the worker thread
  parentPort.on('message', (msg) => {
    // Respond back with a message
    parentPort.postMessage(`Worker received: ${msg}`);
  });
}

Important Notes

Worker threads run in separate memory, so you must send messages to share data.

Use isMainThread to check if code is running in the main or worker thread.

Worker threads help keep your app fast by doing heavy work in the background.

Summary

Worker threads let you run code in parallel without blocking your main program.

You create a worker with new Worker() and communicate using messages.

This helps your app stay responsive during heavy tasks.

Practice

1. What is the main purpose of using worker_threads in Node.js?

easy

A. To handle HTTP requests faster

B. To simplify asynchronous callbacks

C. To manage database connections

D. To run code in parallel without blocking the main thread

Solution

1. Step 1: Understand worker threads role

   Worker threads allow running JavaScript code in parallel threads separate from the main thread.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated tasks; worker threads specifically help avoid blocking the main thread.

3. Final Answer:

   To run code in parallel without blocking the main thread -> Option D

4. Quick Check:

   Parallel code execution = A [OK]

Hint: Worker threads run code parallel to main thread [OK]

Common Mistakes:

• Confusing worker threads with async callbacks
• Thinking worker threads manage HTTP or DB tasks directly

2. Which of the following is the correct way to import the Worker class from the worker_threads module?

easy

A. const Worker = require('worker_threads');

B. import Worker from 'worker_threads';

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

D. const Worker = require('worker_threads').worker;

Solution

1. Step 1: Recall correct import syntax

   The Worker class is a named export, so we use destructuring: const { Worker } = require('worker_threads');

2. Step 2: Check other options

   const Worker = require('worker_threads'); assigns the entire module object, not the Worker class. import Worker from 'worker_threads'; uses ES module syntax which requires extra config. const Worker = require('worker_threads').worker; uses wrong property name.

3. Final Answer:

   const { Worker } = require('worker_threads'); -> Option C

4. Quick Check:

   Destructure Worker from module = D [OK]

Hint: Use destructuring to import Worker from worker_threads [OK]

Common Mistakes:

• Using wrong property name like 'worker' instead of 'Worker'
• Mixing CommonJS and ES module syntax incorrectly

3. What will be the output of the following code snippet?

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. From worker: Hello World

B. From worker: Hello

C. SyntaxError

D. No output

Solution

1. Step 1: Understand main and worker thread roles

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

2. Step 2: Trace message passing

   Worker receives 'Hello', appends ' World', and sends back 'Hello World'. Main thread logs this message.

3. Final Answer:

   From worker: Hello World -> Option A

4. Quick Check:

   Message sent + ' World' logged = B [OK]

Hint: Worker appends ' World' and sends back message [OK]

Common Mistakes:

• Expecting original message without modification
• Confusing main thread and worker thread roles
• Missing event listeners for messages

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 should be absolute or URL

B. Missing event listener for 'error' event

C. Cannot create Worker with a string filename

D. Cannot call postMessage on Worker instance

Solution

1. Step 1: Check Worker constructor argument

   The Worker constructor expects an absolute path or a URL, not just a relative string like 'worker.js'.

2. Step 2: Validate other options

   Cannot create Worker with a string filename is incorrect because Worker can be created with a filename if path is correct. Missing event listener for 'error' event is good practice but not an error. Cannot call postMessage on Worker instance is wrong; postMessage is valid on Worker.

3. Final Answer:

   Worker file path should be absolute or URL -> Option A

4. Quick Check:

   Worker needs absolute path or URL = C [OK]

Hint: Use absolute path or URL for Worker file [OK]

Common Mistakes:

• Using relative paths without resolving them
• Ignoring error event listeners
• Thinking postMessage is invalid on Worker

5. You want to create a worker thread that performs a CPU-heavy calculation and sends the result back. Which approach correctly creates the worker and handles the result asynchronously?

hard

A. Use new Worker() without arguments and call worker.send() to communicate

B. Use new Worker('./calc.js') with worker.on('message', callback) and send data via worker.postMessage()

C. Use require('worker_threads').run() to start the worker and get a promise

D. Create a child process with child_process.fork() and communicate with worker.postMessage()

Solution

1. Step 1: Identify correct Worker creation and communication

   Creating a worker with new Worker('./calc.js') and using worker.on('message') plus worker.postMessage() is the standard pattern.

2. Step 2: Eliminate incorrect options

   Use new Worker() without arguments and call worker.send() to communicate is invalid because Worker requires a filename or code. Use require('worker_threads').run() to start the worker and get a promise is incorrect; no run() method exists. Create a child process with child_process.fork() and communicate with worker.postMessage() uses child_process, not worker_threads, and postMessage is not valid on child processes.

3. Final Answer:

   Use new Worker('./calc.js') with worker.on('message', callback) and send data via worker.postMessage() -> Option B

4. Quick Check:

   Worker with filename + message events = A [OK]

Hint: Use new Worker(filename) and message events for communication [OK]

Common Mistakes:

• Trying to create Worker without filename
• Confusing child_process with worker_threads
• Using non-existent Worker methods