Why worker threads matter in Node.js - See It in Action

Why Worker Threads Matter in Node.js

📖 Scenario: You are building a Node.js application that needs to perform a heavy calculation without freezing the main program. Normally, Node.js runs code on a single thread, so heavy tasks can make the app slow or unresponsive.Worker threads let you run heavy tasks in the background, like having a helper do the hard work while you keep talking to your users.

🎯 Goal: Build a simple Node.js program that uses a Worker thread to calculate the sum of numbers from 1 to 1,000,000 without blocking the main thread.

📋 What You'll Learn

Create a variable with the number 1,000,000

Create a worker thread using the worker_threads module

Send the number to the worker thread

Receive the result from the worker thread and log it

💡 Why This Matters

🌍 Real World

Worker threads help keep Node.js applications responsive by running heavy tasks in the background, like image processing or data crunching, while the main thread handles user requests smoothly.

💼 Career

Understanding worker threads is important for backend developers working with Node.js to build scalable and efficient applications that handle heavy computations without slowing down.

1

Set up the number to sum

Create a variable called maxNumber and set it to 1000000.

Node.js

# Create a variable called maxNumber and set it to 1000000
# Your code here

Hint

Use const maxNumber = 1000000; to create the variable.

2

Import Worker and create a worker thread

Import Worker and isMainThread from the worker_threads module. Then create a new Worker instance that runs the current file if isMainThread is true.

Node.js

const maxNumber = 1000000;
// Import Worker and isMainThread from 'worker_threads'
// Create a Worker instance if isMainThread is true
# Your code here

Hint

Use const { Worker, isMainThread, parentPort } = require('worker_threads'); and new Worker(__filename);

3

Send data to worker and calculate sum

Inside the if (isMainThread) block, send maxNumber to the worker using worker.postMessage(maxNumber). Outside that block, add code for the worker thread to listen for messages with parentPort.on('message') and calculate the sum of numbers from 1 to the received number.

Node.js

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

if (isMainThread) {
  const worker = new Worker(__filename);
  // Send maxNumber to worker
  // Your code here
} else {
  // Listen for message and calculate sum
  // Your code here
}

Hint

Use worker.postMessage(maxNumber); to send data and parentPort.on('message', (max) => { ... }); to receive it in the worker.

4

Receive result from worker and log it

In the if (isMainThread) block, add a listener for worker.on('message') to receive the sum result from the worker and log it using console.log.

Node.js

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

if (isMainThread) {
  const worker = new Worker(__filename);
  worker.postMessage(maxNumber);
  // Listen for message from worker and log it
  // Your code here
} else {
  parentPort.on('message', (max) => {
    let sum = 0;
    for (let i = 1; i <= max; i++) {
      sum += i;
    }
    parentPort.postMessage(sum);
  });
}

Hint

Use worker.on('message', (result) => { console.log(...); }); to get the result and show it.

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