Worker Threads

This lesson covers Worker Threads. You do not need to memorize everything. Understand the flow first.

What you will learn

• What worker threads means — in normal words, not textbook words
• How it works step by step
• Code you can run today on your laptop
• Where teams use this in real projects

Before you start

• Software: Node.js LTS from nodejs.org, VS Code, and a terminal
• Knowledge: Earlier lessons in this Node.js course
• Previous lesson: Async Iterators — Complete Guide

Explain it simply

Worker threads run JavaScript on another thread for CPU-heavy work so your main thread stays free for HTTP requests.

Why developers use this

• Node stays fast under load
• Required for files and databases
• Common in interviews

How it works (step by step)

1. Your code starts a task (read file, query DB, timer).
2. Node continues other work instead of waiting idle.
3. When the task finishes, your callback, Promise, or await runs.
4. Errors go in catch or .catch() — never ignore them.

Code example — type this yourself

const { Worker } = require('worker_threads');
const worker = new Worker('./worker.js');
worker.on('message', (msg) => console.log('result', msg));

Put heavy math or image work in worker.js. The main file keeps serving users.

What each part does

• const { Worker } = require('worker_threads'); — Loads a built-in module or package you installed with npm.
• const worker = new Worker('./worker.js'); — Line 2: runs as written.
• worker.on('message', (msg) => console.log('result', msg)); — Event pattern: listen with on, trigger with emit.

Real life: where Worker Threads shows up

An online store uses Worker Threads so hundreds of users can check order status at once. While one request waits for the database, Node handles other users instead of freezing. Start small: one feature working beats a perfect architecture on paper.

Try it yourself — hands-on

1. Create a new file (e.g. worker-threads-demo.js) in an empty folder
2. Type the example code for Worker Threads yourself — typing helps memory
3. Run node on that file and read the output
4. Change one line (a value, a message, a route path) and run again to see what breaks or improves

Common mistakes (avoid these)

• Skipping the terminal — Worker Threads only feels easy after you run code yourself.

Interview note

Interviewers often ask: “What is Worker Threads?” Answer in one sentence, then give a tiny example you actually ran.

Summary

• You can explain Worker Threads in your own words
• You ran working code — not just read about it
• You know one mistake to avoid and one real place teams use this