Why child processes are needed in Node.js - See It in Action

Why Child Processes Are Needed in Node.js

📖 Scenario: Imagine you have a Node.js server that needs to do a heavy task like resizing many images or processing large files. Doing this in the main program can make the server slow or unresponsive.

🎯 Goal: You will create a simple Node.js program that uses a child process to run a separate script. This shows how child processes help keep the main program fast and responsive.

📋 What You'll Learn

Create a main Node.js file that starts a child process

Create a separate script file that the child process will run

Use the child_process module to spawn the child process

Show how the main process stays responsive while the child process runs

💡 Why This Matters

🌍 Real World

Web servers often need to handle many users and heavy tasks without slowing down. Child processes help by running heavy work separately.

💼 Career

Understanding child processes is important for backend developers to build scalable and responsive Node.js applications.

1

Create the child script file

Create a file named childTask.js that contains a function to simulate a heavy task by using setTimeout to wait 3000 milliseconds, then logs 'Child process task completed'.

Node.js

// Your code here to create childTask.js
// Use setTimeout to simulate a 3-second task
// Log 'Child process task completed' after the wait

Hint

Use setTimeout to delay the message and simulate work.

2

Set up the main Node.js file

Create a file named main.js and import the spawn function from the child_process module.

Node.js

// Your code here to import spawn from child_process
const { spawn } = require('child_process');

Hint

Use require('child_process') to get spawn.

3

Spawn the child process to run the task

In main.js, use spawn to start a child process that runs node with the argument childTask.js. Add an event listener to the child process's stdout to print any data it sends. Also, add a listener for the close event to log 'Child process exited'.

Node.js

const child = spawn('node', ['childTask.js']);
// Add listener for child.stdout data
// Add listener for child close event

Hint

Use child.stdout.on('data', ...) to get output from the child process.

4

Show main process stays responsive

In main.js, add a setInterval that logs 'Main process is running' every 1000 milliseconds. This shows the main program keeps working while the child process runs.

Node.js

setInterval(() => {
  // Your code here to log 'Main process is running'
}, 1000);

Hint

Use setInterval to repeatedly log a message every second.

Practice

1. Why do Node.js applications use child processes?

easy

A. To make the app load faster on the internet

B. To reduce the size of the app files

C. To run heavy tasks without freezing the main app

D. To automatically update Node.js version

Solution

1. Step 1: Understand Node.js single-threaded nature

   Node.js runs JavaScript in a single thread, so heavy tasks can block the app.

2. Step 2: Role of child processes

   Child processes run tasks separately, so the main app stays responsive.

3. Final Answer:

   To run heavy tasks without freezing the main app -> Option C

4. Quick Check:

   Child processes prevent freezing = B [OK]

Hint: Child processes keep main app responsive during heavy work [OK]

Common Mistakes:

• Thinking child processes speed up internet loading
• Confusing file size with process management
• Believing child processes update Node.js automatically

2. Which of the following is the correct way to create a child process in Node.js?

easy

A. const child = require('child_process').fork('script.js');

B. const child = require('child_process').start('script.js');

C. const child = require('child_process').run('script.js');

D. const child = require('child_process').execute('script.js');

Solution

1. Step 1: Recall Node.js child process methods

   The 'child_process' module has methods like fork(), spawn(), exec(), but not start() or run().

2. Step 2: Identify correct method for creating a child process running a script

   fork() is used to create a new Node.js process running a script file.

3. Final Answer:

   const child = require('child_process').fork('script.js'); -> Option A

4. Quick Check:

   fork() creates child process = A [OK]

Hint: Use fork() to create child Node.js processes [OK]

Common Mistakes:

• Using non-existent methods like start() or run()
• Confusing exec() with fork() for script processes
• Forgetting to require 'child_process' 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('Message from child:', msg);
});
child.send('Hello');

Assuming child.js sends back the message { reply: 'Hi' } when it receives a message.

medium

A. No output because child.js is not executed

B. Message from child: Hello

C. Error: child.send is not a function

D. Message from child: { reply: 'Hi' }

Solution

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

   The parent sends 'Hello' to child.js, which replies with { reply: 'Hi' }.

2. Step 2: Check event listener for 'message'

   The parent listens for messages from child and logs them with prefix 'Message from child:'.

3. Final Answer:

   Message from child: { reply: 'Hi' } -> Option D

4. Quick Check:

   Child replies logged correctly = D [OK]

Hint: Child sends message, parent logs with 'Message from child:' prefix [OK]

Common Mistakes:

• Confusing sent and received messages
• Expecting error from child.send() which is valid
• Assuming child.js does not run without error

4. Identify the error in this Node.js code using child processes:

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

medium

A. Calling child.send() before setting up 'message' event listener

B. No error; code is correct

C. Not handling 'exit' event of child process

D. Missing require statement for 'child_process' module

Solution

1. Step 1: Check order of send() and event listeners

   It's valid to call send() before setting up 'message' listener; messages will queue.

2. Step 2: Verify required event handlers and module import

   Module is required correctly; 'error' event is handled; 'exit' event is optional.

3. Final Answer:

   No error; code is correct -> Option B

4. Quick Check:

   Code follows child process patterns = C [OK]

Hint: send() can be called anytime; event listeners catch messages/errors [OK]

Common Mistakes:

• Thinking send() must come after 'message' listener
• Expecting mandatory 'exit' event handling
• Missing module import (not in this code)

5. You want to perform a CPU-heavy task in Node.js without blocking the main event loop. Which approach best uses child processes to achieve this?

hard

A. Use fork() to run the heavy task in a separate process and communicate results via messages

B. Run the heavy task directly in the main thread and use setTimeout to delay it

C. Use exec() to run a shell command that blocks the main thread

D. Use require() to load the heavy task module synchronously

Solution

1. Step 1: Identify how to avoid blocking main event loop

   Heavy CPU tasks block the single-threaded main loop, causing freezes.

2. Step 2: Use child processes to run heavy tasks separately

   fork() creates a separate Node.js process to run the task without blocking.

3. Step 3: Communicate results safely

   Use message passing between main and child process to get results asynchronously.

4. Final Answer:

   Use fork() to run the heavy task in a separate process and communicate results via messages -> Option A

5. Quick Check:

   fork() isolates heavy tasks = A [OK]

Hint: fork() runs heavy tasks separately, keeping main loop free [OK]

Common Mistakes:

• Using setTimeout to delay heavy tasks (does not prevent blocking)
• Using exec() which can block main thread
• Loading heavy tasks synchronously with require()