fork for Node.js child processes in Node.js - Step-by-Step Execution

Concept Flow - fork for Node.js child processes

Main Process Starts

↓

Call fork() to create Child

↓

Child Process Runs Separate Script

↓

Parent and Child Communicate via Messages

↓

Child Sends Message to Parent

↓

Parent Receives and Handles Message

↓

Child Exits

↓

Parent Detects Child Exit

↓

End

The main process uses fork() to create a child process running a separate script. They communicate by sending messages until the child exits and the parent detects it.

Execution Sample

Node.js

const { fork } = require('child_process');
const child = fork('child.js');
child.on('message', msg => console.log('Parent got:', msg));
child.send('Hello Child');

This code forks a child process running 'child.js', sends it a message, and listens for messages from the child.

Execution Table

Step	Action	Process	Message Sent	Message Received	State Change
1	Main process starts	Parent			Parent running
2	Call fork('child.js')	Parent			Child process created
3	Child process starts running 'child.js'	Child			Child running
4	Parent sends message 'Hello Child'	Parent	Hello Child		Message sent to child
5	Child receives 'Hello Child'	Child		Hello Child	Child processes message
6	Child sends message 'Hello Parent'	Child	Hello Parent		Message sent to parent
7	Parent receives 'Hello Parent'	Parent		Hello Parent	Parent processes message
8	Child exits	Child			Child process ends
9	Parent detects child exit	Parent			Parent cleans up
10	Execution ends	Parent			No more child processes

💡 Child process exits and parent detects it, ending communication.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
child	undefined	ChildProcess object created	ChildProcess object with message sent	ChildProcess object with message received	ChildProcess object ended

Key Moments - 3 Insights

Why does the child process run a separate script instead of the same code as the parent?

Because fork() creates a new Node.js process running the specified script file separately, allowing independent execution and communication. See execution_table steps 2 and 3.

How do parent and child communicate after forking?

They send messages using child.send() and listen with 'message' event handlers, as shown in steps 4-7 in the execution_table.

What happens when the child process exits?

The parent detects the child's exit event and can clean up resources, shown in steps 8 and 9.

Visual Quiz - 3 Questions

Look at the execution_table, what message does the parent send to the child at step 4?

A "Start"

B "Hello Parent"

C "Hello Child"

D "Exit"

💡 Hint

Check the 'Message Sent' column at step 4 in the execution_table.

At which step does the child process send a message back to the parent?

A Step 5

B Step 6

C Step 7

D Step 8

💡 Hint

Look for 'Message Sent' by the child in the execution_table.

If the child never sends a message back, which step would be missing in the execution_table?

A Step 6

B Step 4

C Step 5

D Step 9

💡 Hint

Step 6 shows the child sending a message to the parent.

Concept Snapshot

fork() creates a new Node.js child process running a separate script.
Parent and child communicate by sending messages with send() and 'message' events.
Child runs independently but can send data back to parent.
Parent listens for child's exit to clean up.
Useful for parallel tasks without blocking main process.

Full Transcript

In Node.js, fork() creates a new child process running a separate JavaScript file. The parent process can send messages to the child using child.send(), and the child listens for these messages. The child can also send messages back to the parent. This communication happens through an IPC channel. When the child finishes its work, it exits, and the parent detects this exit event to clean up. This allows running tasks in parallel without blocking the main process.

Practice

1. What does the fork method in Node.js do?

easy

A. It merges two running processes into one.

B. It pauses the current process for a set time.

C. It creates a new Node.js process to run a separate script.

D. It stops the current process immediately.

Solution

1. Step 1: Understand the purpose of fork

   The fork method is used to create a new child process that runs a separate Node.js script independently.

2. Step 2: Compare options with the definition

   Only It creates a new Node.js process to run a separate script. correctly describes this behavior. Other options describe unrelated actions like pausing, merging, or stopping processes.

3. Final Answer:

   It creates a new Node.js process to run a separate script. -> Option C

4. Quick Check:

   fork creates child process = C [OK]

Hint: Remember: fork means start a new Node.js process [OK]

Common Mistakes:

• Thinking fork pauses or merges processes
• Confusing fork with setTimeout or kill
• Assuming fork runs code in the same process

2. Which of the following is the correct way to import and use fork from the child_process module in Node.js?

easy

A. const fork = require('child_process').fork();

B. const { fork } = require('child_process');

C. import fork from 'child_process';

D. const fork = require('child_process').Fork;

Solution

1. Step 1: Recall correct import syntax for fork

   In Node.js CommonJS, fork is a named export from child_process, so we use destructuring: const { fork } = require('child_process');

2. Step 2: Analyze each option

   const fork = require('child_process').fork(); calls fork() immediately, which is incorrect. import fork from 'child_process'; uses ES module syntax without proper setup. const fork = require('child_process').fork; assigns the function but misses destructuring. const { fork } = require('child_process'); is correct.

3. Final Answer:

   const { fork } = require('child_process'); -> Option B

4. Quick Check:

   Destructure fork from child_process = A [OK]

Hint: Use curly braces to import fork: const { fork } = require(...) [OK]

Common Mistakes:

• Calling fork() during import
• Using ES module import without config
• Not destructuring fork from module

3. What will be the output of this Node.js code snippet?

const { fork } = require('child_process');
const child = fork('child.js');
child.on('message', (msg) => {
  console.log('Parent received:', msg);
});
child.send('Hello Child');

// child.js content:
// process.on('message', (msg) => {
//   process.send(msg + ' from Child');
// });

medium

A. No output because child.js is missing

B. Parent received: Hello Child

C. Error: child.send is not a function

D. Parent received: Hello Child from Child

Solution

1. Step 1: Understand message passing between parent and child

   The parent sends 'Hello Child' to the child process. The child listens for messages and replies by appending ' from Child'.

2. Step 2: Trace the output

   The parent listens for messages from the child and logs them. So it logs: 'Parent received: Hello Child from Child'.

3. Final Answer:

   Parent received: Hello Child from Child -> Option D

4. Quick Check:

   Message sent and replied correctly = D [OK]

Hint: Child replies with modified message; parent logs it [OK]

Common Mistakes:

• Assuming child.send is undefined
• Ignoring message event listeners
• Thinking output is only 'Hello Child'

4. Identify the error in this code using fork and how to fix it:

const { fork } = require('child_process');
const child = fork('child.js');
child.send('start');
child.on('message', (msg) => {
  console.log(msg);
});

Assuming child.js does not listen for messages.

medium

A. Error because child.js must listen for messages before parent sends.

B. No error; code works fine.

C. Error because fork requires a callback function.

D. Error because child.send is not a function.

Solution

1. Step 1: Check message handling in child.js

   If child.js does not listen for messages, sending messages from parent has no effect and may cause unexpected behavior.

2. Step 2: Fix by adding message listener in child.js

   Child script should have process.on('message', (msg) => { ... }) to handle incoming messages properly.

3. Final Answer:

   Error because child.js must listen for messages before parent sends. -> Option A

4. Quick Check:

   Child must listen for messages = A [OK]

Hint: Child must handle messages before parent sends [OK]

Common Mistakes:

• Assuming fork needs callback
• Thinking child.send is undefined
• Ignoring child.js message listener

5. You want to run two separate scripts worker1.js and worker2.js in parallel using fork. You also want to collect their results and print "All done" only after both finish. Which approach correctly achieves this?

hard

A. Fork both scripts, listen for 'exit' events on both, then print after both exit.

B. Fork one script, then fork the second inside the first child's 'exit' event.

C. Fork both scripts and print "All done" immediately after forking.

D. Use exec instead of fork to run scripts sequentially.

Solution

1. Step 1: Understand parallel execution with fork

   Forking both scripts starts them in parallel. To know when both finish, listen for their 'exit' events.

2. Step 2: Wait for both exit events before printing

   Track both exits with counters or flags, then print "All done" only after both have exited.

3. Final Answer:

   Fork both scripts, listen for 'exit' events on both, then print after both exit. -> Option A

4. Quick Check:

   Wait for both exits before printing = B [OK]

Hint: Use 'exit' events on both children to sync completion [OK]

Common Mistakes:

• Starting second child inside first child's exit
• Printing before children finish
• Using exec for parallel child processes