Creating worker threads in Node.js - Visual Walkthrough

Concept Flow - Creating worker threads

Main Thread Starts

↓

Create Worker Thread

↓

Worker Thread Runs Code

↓

Worker Sends Message to Main

↓

Main Receives Message

↓

Main and Worker Continue or Exit

The main thread creates a worker thread that runs code separately. They communicate by sending messages back and forth.

Execution Sample

Node.js

import { Worker } from 'node: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));

This code creates a worker thread that sends a message to the main thread, which then logs it.

Execution Table

Step	Action	Thread	Message Sent	Message Received	Output
1	Main thread starts	Main
2	Create worker thread with inline code	Main
3	Worker thread starts running code	Worker
4	Worker sends message 'Hello from worker'	Worker	Hello from worker
5	Main thread receives message	Main		Hello from worker
6	Main thread logs message	Main			Hello from worker
7	Both threads continue or exit	Main & Worker

💡 Execution stops after message is logged and no more code runs.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	Final
worker	undefined	Worker instance created	Worker running	Message received event set	Worker instance exists

Key Moments - 3 Insights

Why does the worker code run separately from the main thread?

Because the worker thread runs its own event loop and code independently, as shown in steps 3 and 4 where the worker sends a message without blocking the main thread.

How does the main thread get the message from the worker?

The main thread listens for the 'message' event on the worker object, as shown in step 5 where it receives 'Hello from worker'.

What does the { eval: true } option do when creating the worker?

It allows passing the worker code as a string to be evaluated, instead of loading from a separate file, as seen in step 2.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the worker send a message to the main thread?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Check the 'Message Sent' column in the execution table.

According to the variable tracker, what is the state of the 'worker' variable after step 2?

A Undefined

B Message received event set

C Worker instance created

D Worker running

💡 Hint

Look at the 'After Step 2' column for 'worker' in the variable tracker.

If the main thread did not listen for messages, what would happen in the execution table?

A Step 5 would not show a message received

B Step 4 would not send a message

C Step 6 would log the message anyway

D Worker thread would not start

💡 Hint

Refer to the 'Message Received' column in the execution table.

Concept Snapshot

Creating worker threads in Node.js:
- Use 'Worker' from 'worker_threads' module
- Pass code or file to run in worker
- Workers run code separately from main thread
- Communicate via 'postMessage' and 'message' events
- Use { eval: true } to run inline code
- Main thread listens for messages to receive data

Full Transcript

In Node.js, creating worker threads lets you run code in parallel without blocking the main thread. The main thread creates a Worker instance, passing code to run. The worker runs independently and can send messages back to the main thread using postMessage. The main thread listens for these messages with the 'message' event. This allows communication between threads. Using the { eval: true } option lets you pass code as a string instead of a file. This example shows the main thread creating a worker that sends a greeting message, which the main thread logs. This way, heavy or blocking tasks can run in the worker without freezing the main program.