Receiving results from workers in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main way to receive results from worker threads in Node.js?

You listen for the 'message' event on the worker instance to receive data sent back from the worker thread.

beginner

How do you send data from a worker thread back to the main thread?

Use the worker's parentPort.postMessage() method inside the worker to send data back to the main thread.

intermediate

Why is it important to handle errors when receiving results from workers?

Because workers run in separate threads, errors can happen independently. Handling errors prevents crashes and helps debug issues.

beginner

What Node.js module do you use to create worker threads?

You use the 'worker_threads' module to create and manage worker threads.

intermediate

How can you ensure the main thread waits for a worker's result before continuing?

You can wrap the worker's message event in a Promise and await it, so the main thread pauses until the worker sends its result.

Which event do you listen to on a worker to get results?

A data

B response

C result

D message

The 'message' event is emitted when the worker sends data back to the main thread.

How do you send data from the main thread to a worker?

A worker.emit()

B worker.send()

C worker.postMessage()

D worker.write()

The main thread uses worker.postMessage() to send data to the worker.

Which module must you import to use worker threads?

A worker_threads

B cluster

C child_process

D events

The 'worker_threads' module provides the Worker class for threading.

What method inside a worker sends messages back to the main thread?

A parentPort.send()

B parentPort.postMessage()

C process.send()

D worker.postMessage()

Inside a worker, parentPort.postMessage() sends data back to the main thread.

How can you handle worker results asynchronously in the main thread?

A Wrap the message event in a Promise and await it

B Use setTimeout to wait for results

C Call worker.wait() method

D Use synchronous blocking calls

Wrapping the message event in a Promise lets you await the worker's result cleanly.

Explain how the main thread receives and handles results from a worker thread in Node.js.

Think about events and message passing between threads.

Describe how you can make the main thread wait for a worker's result before continuing execution.

Consider how async code can pause until data arrives.

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