Why worker threads matter in Node.js - Quick Recap

Recall & Review

beginner

What is the main reason to use worker threads in Node.js?

Worker threads allow Node.js to run JavaScript code in parallel, so heavy tasks don't block the main thread and slow down the app.

beginner

How do worker threads improve Node.js performance?

They let CPU-heavy tasks run in separate threads, so the main thread stays free to handle user requests and events smoothly.

intermediate

What problem do worker threads solve compared to the default Node.js model?

Node.js runs on a single thread by default, so long tasks block everything. Worker threads let you run tasks in parallel to avoid this blocking.

advanced

Can worker threads share memory in Node.js?

Yes, worker threads can share memory using SharedArrayBuffer, which helps them communicate efficiently without copying data.

intermediate

Why might you choose worker threads over child processes in Node.js?

Worker threads are lighter and faster because they share memory, while child processes are heavier and communicate via messaging only.

What is the main benefit of using worker threads in Node.js?

A Run CPU-heavy tasks without blocking the main thread

B Make HTTP requests faster

C Store data in a database

D Improve CSS styling

Worker threads let you run heavy tasks in parallel, so the main thread stays responsive.

How do worker threads communicate with the main thread?

A By sharing memory or sending messages

B By writing files to disk

C By opening new browser tabs

D By changing environment variables

Worker threads can share memory using SharedArrayBuffer or send messages to communicate.

Which Node.js feature runs JavaScript code on a single thread by default?

A HTTP server

B Worker threads

C Event loop

D Child processes

The event loop runs on a single thread, handling asynchronous tasks.

Compared to child processes, worker threads are:

A Heavier and slower

B Lighter and faster

C Exactly the same

D Not available in Node.js

Worker threads share memory and are lighter than child processes, which use separate memory.

Which of these is NOT a use case for worker threads?

A Running background tasks without blocking

B Running CPU-intensive calculations

C Performing image processing

D Handling multiple HTTP requests

Handling HTTP requests is usually done by the main thread; worker threads help with heavy background tasks.

Explain why worker threads matter in Node.js and how they help improve app performance.

Think about how a busy kitchen chef can get help to cook faster.

Describe the differences between worker threads and child processes in Node.js.

Compare sharing a room versus living in separate houses.

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