Receiving results from workers in Node.js

Introduction

Workers help run tasks in the background without stopping your main program. Receiving results from workers lets you get the answers or data they finish.

When you want to do heavy calculations without freezing your app.

When you need to run multiple tasks at the same time and collect their results.

When you want to keep your app responsive while workers do background jobs.

When you want to split a big job into smaller parts and combine the results.

When you want to handle tasks like file processing or data fetching in parallel.

Syntax

Node.js

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

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

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

worker.postMessage('start');

The message event listens for results sent from the worker.

Use postMessage to send data or commands to the worker.

Examples

Listen for any message from the worker and print it.

Node.js

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

Send a task object to the worker to start processing.

Node.js

worker.postMessage({ task: 'calculate', numbers: [1, 2, 3] });

Handle errors coming from the worker to avoid crashes.

Node.js

worker.on('error', (err) => {
  console.error('Worker error:', err);
});

Sample Program

This program creates a worker that calculates the square of a number sent from the main thread. The main thread sends the number 10, and the worker sends back 100.

Node.js

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

if (isMainThread) {
  // Main thread code
  const worker = new Worker(__filename);

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

  worker.on('error', (err) => {
    console.error('Worker error:', err);
  });

  worker.postMessage(10); // Send number to worker
} else {
  // Worker thread code
  parentPort.on('message', (num) => {
    // Calculate square
    const square = num * num;
    parentPort.postMessage(square); // Send result back
  });
}

Important Notes

Always listen for the error event on workers to catch problems.

Workers communicate only by sending messages; you cannot share variables directly.

Use isMainThread to separate main and worker code in the same file.

Summary

Workers run tasks in the background to keep your app smooth.

You receive results by listening to the message event from the worker.

Send data to workers using postMessage and handle errors properly.

Practice

1. In Node.js, how do you receive results from a worker thread?

easy

A. By using console.log inside the worker

B. By calling worker.getResult() method

C. By listening to the message event on the worker

D. By reading from a shared file

Solution

1. Step 1: Understand worker communication

   Workers send results back to the main thread using messages.

2. Step 2: Use the correct event listener

   The main thread listens to the message event on the worker to receive data.

3. Final Answer:

   By listening to the message event on the worker -> Option C

4. Quick Check:

   message event = D [OK]

Hint: Remember: workers send data via 'message' events [OK]

Common Mistakes:

• Trying to call a non-existent method like getResult()
• Expecting console.log output to be received
• Reading results from files instead of messages

2. Which of the following is the correct syntax to listen for messages from a worker in Node.js?

easy

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

B. worker.listen('message', (result) => { console.log(result); });

C. worker.addEventListener('message', (result) => { console.log(result); });

D. worker.receive('message', (result) => { console.log(result); });

Solution

1. Step 1: Recall Node.js worker event syntax

   Node.js workers use the on method to listen for events.

2. Step 2: Identify the correct event and method

   The event to receive data is message, and the syntax is worker.on('message', callback).

3. Final Answer:

   worker.on('message', (result) => { console.log(result); }); -> Option A

4. Quick Check:

   worker.on('message') = A [OK]

Hint: Use worker.on('message', callback) to get results [OK]

Common Mistakes:

• Using non-existent methods like listen or receive
• Confusing browser event syntax with Node.js
• Using addEventListener which is not in Node.js workers

3. What will be logged to the console when this Node.js worker code runs?

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

medium

A. undefined

B. No output

C. Error: parentPort is not defined

D. Hello from worker

Solution

1. Step 1: Understand worker code execution

   The worker sends a message 'Hello from worker' using parentPort.postMessage.

2. Step 2: Check main thread message listener

   The main thread listens to the message event and logs the received message.

3. Final Answer:

   Hello from worker -> Option D

4. Quick Check:

   postMessage sends 'Hello from worker' = B [OK]

Hint: postMessage sends data, main thread logs it on 'message' event [OK]

Common Mistakes:

• Expecting no output because of missing event listener
• Confusing parentPort usage causing errors
• Assuming worker code runs in main thread

4. Identify the error in this Node.js worker communication code:

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

medium

A. Cannot call postMessage on the worker instance

B. postMessage should be called on parentPort inside worker, not on worker instance

C. Missing error event listener on worker

D. The worker file path is incorrect

Solution

1. Step 1: Understand where postMessage is called

   In Node.js, postMessage is called on parentPort inside the worker, not on the worker instance in main thread.

2. Step 2: Identify correct communication method

   The main thread uses worker.postMessage() to send messages to the worker, but inside the worker, parentPort.postMessage() sends messages back.

3. Final Answer:

   postMessage should be called on parentPort inside worker, not on worker instance -> Option B

4. Quick Check:

   postMessage usage inside worker = C [OK]

Hint: postMessage on worker sends to worker; inside worker use parentPort.postMessage [OK]

Common Mistakes:

• Confusing where to call postMessage
• Ignoring error event listeners
• Assuming worker file path is wrong without evidence

5. You want to receive multiple results from a worker that sends messages repeatedly. Which approach correctly handles this in Node.js?

const { Worker } = require('worker_threads');
const worker = new Worker('./worker.js');
// What should you do here to receive all messages?

hard

A. Use worker.on('message', (msg) => { console.log(msg); }); to listen continuously

B. Call worker.once('message', (msg) => { console.log(msg); }); to listen once

C. Use a loop to call worker.postMessage repeatedly

D. Use setTimeout to poll worker for messages

Solution

1. Step 1: Understand event listeners for multiple messages

   Using worker.on('message') listens continuously for all messages sent by the worker.

2. Step 2: Compare with other options

   once listens only once, loops or polling are unnecessary and inefficient for receiving messages.

3. Final Answer:

   Use worker.on('message', (msg) => { console.log(msg); }); to listen continuously -> Option A

4. Quick Check:

   Continuous message listening = A [OK]

Hint: Use worker.on('message') for all messages, not once or polling [OK]

Common Mistakes:

• Using once instead of on for multiple messages
• Trying to poll worker instead of event listening
• Confusing sending messages with receiving them