Why child processes are needed in Node.js - Quick Recap

Recall & Review

beginner

What is a child process in Node.js?

A child process is a separate process created by a Node.js application to run tasks independently from the main program, allowing parallel work.

beginner

Why do we need child processes in Node.js?

Child processes help run heavy or blocking tasks without freezing the main program, improving performance and responsiveness.

intermediate

How do child processes improve Node.js application performance?

They allow tasks to run in parallel, so the main program can keep handling other work without waiting for slow tasks to finish.

intermediate

Give an example of a task that benefits from using a child process.

Tasks like image processing, file compression, or running external scripts benefit because they take time and can block the main program if run directly.

beginner

What happens if you run a heavy task directly in the main Node.js process?

The main program becomes unresponsive or slow because Node.js runs code in a single thread by default, blocking other tasks.

What is the main benefit of using child processes in Node.js?

A Run tasks in parallel without blocking the main program

B Make the code shorter

C Automatically fix bugs

D Increase memory usage

Child processes allow running tasks separately so the main program stays responsive.

Which of these tasks is best suited for a child process?

A Image resizing or compression

B Simple math calculation

C Reading a small text file

D Logging a message

Heavy tasks like image processing benefit from child processes to avoid blocking.

What happens if a heavy task runs in the main Node.js process?

A Nothing changes

B The program runs faster

C The program crashes immediately

D The program becomes unresponsive

Heavy tasks block the single thread, making the program unresponsive.

How does Node.js create a child process?

A Using the 'fs' module

B Using the 'child_process' module

C Using the 'http' module

D Using the 'events' module

The 'child_process' module provides methods to create child processes.

Which statement is true about child processes?

A They share the same memory as the main process

B They slow down the main program

C They run independently and communicate via messages

D They cannot run external programs

Child processes run separately and communicate through messages, not shared memory.

Explain why child processes are important in Node.js applications.

Think about how Node.js handles tasks and what happens when a task takes too long.

Describe a scenario where using a child process would improve your Node.js app.

Consider tasks like image processing or running external scripts.

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()