Worker pool pattern in Node.js - Step-by-Step Execution

Concept Flow - Worker pool pattern

Start main thread

↓

Create worker pool

↓

Assign tasks to workers

↓

Worker executes task

↓

Worker sends result back

↓

Main thread collects results

↓

Check if more tasks

↓

Assign next

The main thread creates a pool of workers, assigns tasks to them, collects results, and repeats until all tasks are done, then shuts down the pool.

Execution Sample

Node.js

import { Worker } from 'worker_threads';

const pool = [];
for(let i=0; i<2; i++) pool.push(new Worker('./worker.js'));

pool[0].postMessage('task1');
pool[1].postMessage('task2');

This code creates two workers and sends each a task message to start processing.

Execution Table

Step	Action	Worker State	Main Thread State	Message Passing
1	Create Worker 0	Idle	Pool: [Worker0]	No message
2	Create Worker 1	Idle	Pool: [Worker0, Worker1]	No message
3	Send 'task1' to Worker 0	Busy with task1	Pool unchanged	'task1' sent to Worker0
4	Send 'task2' to Worker 1	Busy with task2	Pool unchanged	'task2' sent to Worker1
5	Worker 0 processes task1	Processing task1	Waiting for result	No message
6	Worker 1 processes task2	Processing task2	Waiting for result	No message
7	Worker 0 sends result	Idle	Received result1	'result1' received from Worker0
8	Worker 1 sends result	Idle	Received result2	'result2' received from Worker1
9	Check for more tasks	Idle	No more tasks, shutdown pool	No message
10	Shutdown workers	Terminated	Pool empty	No message

💡 All tasks processed and results collected, workers shut down.

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 7	Final
pool	[]	[Worker0, Worker1]	[Worker0, Worker1]	[Worker0, Worker1]	[]
Worker0 state	Idle	Busy with task1	Processing task1	Idle	Terminated
Worker1 state	Idle	Busy with task2	Processing task2	Idle	Terminated
Main thread results	[]	[]	[]	[result1]	[result1, result2]

Key Moments - 3 Insights

Why does the main thread wait after sending tasks?

Because workers run tasks asynchronously, the main thread waits to receive results before proceeding, as shown in steps 5 and 6 where workers process tasks while the main thread waits.

What happens if a worker finishes a task before others?

The worker sends its result back and becomes idle, ready for new tasks. This is shown in step 7 where Worker0 finishes and sends result while Worker1 is still processing.

Why do we shut down workers at the end?

To free system resources once all tasks are done, as shown in step 10 where workers terminate after no more tasks remain.

Visual Quiz - 3 Questions

Look at the execution table, what is Worker0's state at step 6?

A Processing task1

B Idle

C Busy with task2

D Terminated

💡 Hint

Check the 'Worker State' column at step 6 in the execution_table.

At which step does the main thread receive the first result?

A Step 5

B Step 8

C Step 7

D Step 10

💡 Hint

Look at the 'Main Thread State' and 'Message Passing' columns for when 'result1' is received.

If we add a third worker, how would the pool variable change after creation?

A pool would have 1 worker

B pool would have 3 workers

C pool would have 2 workers

D pool would be empty

💡 Hint

Refer to the variable_tracker 'pool' row after worker creation steps.

Concept Snapshot

Worker Pool Pattern in Node.js:
- Create multiple Worker threads in a pool.
- Assign tasks to idle workers asynchronously.
- Workers process tasks and send results back.
- Main thread collects results and assigns new tasks.
- Shutdown workers when all tasks complete.

Full Transcript

The Worker Pool Pattern in Node.js helps run multiple tasks in parallel using worker threads. First, the main thread creates a pool of workers. Then, it sends tasks to each worker. Workers run tasks independently and send results back. The main thread waits for these results and can assign more tasks if needed. When all tasks are done, the main thread shuts down the workers to save resources. This pattern improves performance by using multiple threads efficiently.

Practice

1. What is the main purpose of using the worker pool pattern in Node.js?

easy

A. To increase the memory usage by creating many workers

B. To avoid using any background threads or workers

C. To slow down the program by running tasks one after another

D. To run multiple tasks concurrently using a fixed number of workers

Solution

1. Step 1: Understand the worker pool pattern concept

   The worker pool pattern uses a limited number of workers to handle many tasks efficiently without creating too many threads.

2. Step 2: Identify the main goal in Node.js context

   It allows running tasks concurrently but limits the number of workers to keep resource use balanced and improve speed.

3. Final Answer:

   To run multiple tasks concurrently using a fixed number of workers -> Option D

4. Quick Check:

   Worker pool = fixed workers + concurrent tasks [OK]

Hint: Worker pool means fixed workers handle many tasks concurrently [OK]

Common Mistakes:

• Thinking worker pool creates unlimited workers
• Believing it slows down the program
• Confusing it with single-threaded execution

2. Which of the following is the correct way to create a worker pool using Node.js worker_threads module?

easy

A. const { Worker } = require('worker_threads'); const pool = new WorkerPool(4);

B. const pool = new WorkerPool(4); const { Worker } = require('worker_threads');

C. const { Worker } = require('worker_threads'); const pool = WorkerPool(4);

D. const pool = new Worker('worker.js', 4);

Solution

1. Step 1: Import Worker correctly from worker_threads

   The correct import is: const { Worker } = require('worker_threads');

2. Step 2: Create a worker pool instance properly

   Assuming a WorkerPool class exists, it should be instantiated with new WorkerPool(4); to create 4 workers.

3. Final Answer:

   const { Worker } = require('worker_threads'); const pool = new WorkerPool(4); -> Option A

4. Quick Check:

   Correct import + new instance = const { Worker } = require('worker_threads'); const pool = new WorkerPool(4); [OK]

Hint: Import Worker first, then create pool with new keyword [OK]

Common Mistakes:

• Calling WorkerPool without new keyword
• Wrong order of import and instantiation
• Using Worker constructor incorrectly

3. Given this simplified worker pool code snippet, what will be logged to the console?

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

class WorkerPool {
  constructor(size) {
    this.workers = Array(size).fill(null).map(() => new Worker('./worker.js'));
  }
  runTask(task) {
    return new Promise((resolve) => {
      const worker = this.workers.pop();
      worker.once('message', (result) => {
        this.workers.push(worker);
        resolve(result);
      });
      worker.postMessage(task);
    });
  }
}

const pool = new WorkerPool(2);
pool.runTask('task1').then(console.log);
pool.runTask('task2').then(console.log);

medium

A. Runs tasks sequentially, logs task1 then task2

B. Outputs results of task1 and task2 as they complete, order not guaranteed

C. Only task1 result is logged, task2 is ignored

D. Throws an error because workers array is empty after first pop

Solution

1. Step 1: Understand worker allocation and reuse

   The pool starts with 2 workers. Each runTask pops a worker, uses it, then pushes it back after message received.

2. Step 2: Analyze concurrency and output order

   Both tasks run concurrently on separate workers. Results log as tasks complete, order may vary.

3. Final Answer:

   Outputs results of task1 and task2 as they complete, order not guaranteed -> Option B

4. Quick Check:

   Workers reused, tasks run concurrently [OK]

Hint: Workers pop and push back, tasks run in parallel [OK]

Common Mistakes:

• Assuming workers array empties causing error
• Thinking tasks run one after another
• Believing only first task logs

4. Identify the bug in this worker pool code snippet and choose the correct fix:

class WorkerPool {
  constructor(size) {
    this.workers = [];
    for (let i = 0; i < size; i++) {
      this.workers.push(new Worker('./worker.js'));
    }
  }

  runTask(task) {
    if (this.workers.length === 0) {
      throw new Error('No workers available');
    }
    const worker = this.workers.pop();
    worker.once('message', (result) => {
      resolve(result);
      this.workers.push(worker);
    });
    worker.postMessage(task);
  }
}

medium

A. Replace pop() with shift() to get workers in order

B. Remove the check for empty workers array

C. Add a Promise wrapper around runTask and return it

D. Call worker.terminate() after task completes

Solution

1. Step 1: Check runTask return and resolve usage

   runTask uses resolve inside callback but does not return a Promise or define resolve, causing error.

2. Step 2: Fix by wrapping runTask in a Promise and returning it

   Wrap the logic inside return new Promise((resolve) => { ... }) so resolve is defined and caller can await result.

3. Final Answer:

   Add a Promise wrapper around runTask and return it -> Option C

4. Quick Check:

   runTask must return Promise with resolve [OK]

Hint: runTask uses resolve but lacks Promise wrapper [OK]

Common Mistakes:

• Ignoring missing Promise causes runtime error
• Removing worker availability check breaks logic
• Terminating worker too early stops reuse

5. You want to process 10 CPU-heavy tasks using a worker pool of size 3. Which approach best ensures all tasks run efficiently without overloading the system?

hard

A. Create 3 workers, queue tasks, assign next task when a worker finishes

B. Create 10 workers, one per task, and run all at once

C. Run all tasks in the main thread sequentially without workers

D. Create 3 workers but assign all tasks to the first worker only

Solution

1. Step 1: Understand resource limits and worker pool size

   Creating too many workers (10) can overload CPU and memory. Using 3 workers limits resource use.

2. Step 2: Use a task queue to assign tasks as workers become free

   Queue tasks and assign next task to a worker when it finishes ensures all tasks run efficiently without overload.

3. Final Answer:

   Create 3 workers, queue tasks, assign next task when a worker finishes -> Option A

4. Quick Check:

   Fixed workers + queued tasks = efficient processing [OK]

Hint: Use fixed workers and queue tasks for efficiency [OK]

Common Mistakes:

• Creating too many workers causing overload
• Running tasks sequentially wasting concurrency
• Assigning all tasks to one worker blocking others