Why worker threads matter in Node.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use worker threads in Node.js?

Which of the following best explains why worker threads are important in Node.js?

A They automatically optimize memory usage for all Node.js applications.

B They replace the need for asynchronous callbacks in Node.js.

C They allow Node.js to run multiple JavaScript operations in parallel without blocking the main thread.

D They enable Node.js to run on multiple machines at the same time.

💡 Hint

Think about how Node.js handles tasks and what happens when a task takes a long time.

Worker threads let Node.js run JavaScript code in parallel threads. This helps avoid blocking the main thread, which keeps the app responsive.

❓ component_behavior

intermediate

Output of worker thread example

What will be the output of this Node.js code using worker threads?

Node.js

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

if (isMainThread) {
  const worker = new Worker(__filename);
  worker.on('message', message => console.log('From worker:', message));
  console.log('Main thread running');
} else {
  parentPort.postMessage('Hello from worker');
}

A Main thread running

B Main thread running\nFrom worker: Hello from worker

C From worker: Hello from worker\nMain thread running

D From worker: Hello from worker

💡 Hint

Consider the order of console.log calls in main and worker threads.

The main thread logs first, then the worker sends a message back which is logged next.

🔧 Debug

advanced

Identify the error in worker thread usage

What error will this Node.js code produce?

Node.js

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

const worker = new Worker('console.log("Hello")');

A SyntaxError: Unexpected token 'console.log("Hello")'

B ReferenceError: Worker is not defined

C No error, prints 'Hello'

D TypeError: Worker constructor expects a file path or URL

💡 Hint

Check what the Worker constructor expects as input.

The Worker constructor requires a file path or URL, not a string of code.

❓ state_output

advanced

State sharing between main and worker threads

Given this code, what will be the final value of 'counter' in the main thread?

Node.js

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

let counter = 0;

if (isMainThread) {
  const worker = new Worker(__filename, { workerData: counter });
  worker.on('message', value => {
    counter = value;
    console.log('Counter in main:', counter);
  });
} else {
  let localCounter = workerData;
  localCounter += 5;
  parentPort.postMessage(localCounter);
}

A Counter in main: 5

B Counter in main: 1

C Counter in main: undefined

D Counter in main: 0

💡 Hint

Remember that workerData is a copy, not shared memory.

The worker receives a copy of counter (0), adds 5, and sends back 5. The main thread updates its counter to 5.

📝 Syntax

expert

Correct syntax to create a worker thread with inline code

Which option correctly creates a worker thread that runs inline JavaScript code in Node.js?

A new Worker(new URL('data:text/javascript,console.log("Hello")'), { type: 'module' });

B new Worker('console.log("Hello")');

C new Worker(() => console.log('Hello'));

D new Worker({ code: 'console.log("Hello")' });

💡 Hint

Worker constructor accepts a file path, URL, or data URL with type module.

Option A uses a data URL with type 'module' which is the correct way to run inline code in a worker thread.