Single-threaded non-blocking I/O concept in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'single-threaded' mean in Node.js?

It means Node.js runs JavaScript code on one main thread, handling tasks one at a time in a sequence.

beginner

Explain 'non-blocking I/O' in simple terms.

Non-blocking I/O lets Node.js start a task like reading a file, then keep doing other work without waiting for the task to finish.

intermediate

How does Node.js handle multiple I/O operations with a single thread?

Node.js uses an event loop to watch for completed tasks and callbacks to handle results, so it can manage many I/O tasks without waiting.

beginner

Why is single-threaded non-blocking I/O good for web servers?

Because it can handle many users at once without waiting, making servers fast and efficient even with many requests.

intermediate

What happens if a task blocks the single thread in Node.js?

The whole program waits and becomes slow, because no other tasks can run until the blocking task finishes.

What does 'non-blocking' mean in Node.js I/O?

A Node.js waits for each task to finish before starting the next

B Node.js can start a task and do other work without waiting

C Node.js uses multiple threads for each task

D Node.js blocks the main thread during I/O

Non-blocking means Node.js starts a task and continues running other code without waiting for the task to finish.

How many main threads does Node.js use to run JavaScript code?

A One thread

B Two threads

C Multiple threads

D Depends on the CPU cores

Node.js runs JavaScript on a single main thread.

What mechanism does Node.js use to manage I/O tasks without blocking?

A Event loop

B Thread pool

C Synchronous calls

D Blocking queue

The event loop watches for completed tasks and triggers callbacks to handle them.

Why can blocking code slow down a Node.js application?

A Because it runs asynchronously

B Because it uses too many threads

C Because it stops the single thread from doing other work

D Because it uses too much memory

Blocking code stops the single thread, so no other code can run until it finishes.

Which of these is a benefit of Node.js single-threaded non-blocking I/O?

A Runs blocking code faster

B Uses multiple CPU cores automatically

C Requires less memory than other languages

D Handles many requests efficiently

Node.js can handle many requests at once without waiting, making it efficient.

Describe how Node.js uses single-threaded non-blocking I/O to handle multiple tasks.

Think about how Node.js can do many things without waiting for each to finish.

Explain why blocking code is a problem in Node.js and how non-blocking I/O solves it.

Consider what happens when the main thread is busy or free.

Practice

1. What does it mean that Node.js uses a single-threaded non-blocking I/O model?

easy

A. Node.js blocks the main thread until each task completes.

B. Node.js runs one main thread but can handle many tasks without waiting for each to finish.

C. Node.js uses multiple threads to run tasks in parallel.

D. Node.js cannot handle multiple tasks at the same time.

Solution

1. Step 1: Understand single-threaded meaning

   Node.js runs on one main thread, unlike some systems that use many threads.

2. Step 2: Understand non-blocking I/O meaning

   It does not wait for tasks like file reads to finish before moving on; it uses callbacks or events.

3. Final Answer:

   Node.js runs one main thread but can handle many tasks without waiting for each to finish. -> Option B

4. Quick Check:

   Single-threaded + non-blocking = handle many tasks without waiting [OK]

Hint: Single thread means one main path; non-blocking means no waiting [OK]

Common Mistakes:

• Thinking Node.js uses multiple threads for tasks
• Assuming Node.js waits for each task to finish before continuing
• Confusing blocking with non-blocking I/O

2. Which of the following is the correct way to write a non-blocking file read in Node.js?

easy

A. fs.readFile('file.txt', (err, data) => { if (err) throw err; console.log(data); });

B. const data = fs.readFileSync('file.txt'); console.log(data);

C. const data = fs.readFile('file.txt'); console.log(data);

D. fs.readFile('file.txt'); console.log('done');

Solution

1. Step 1: Identify non-blocking syntax

   Non-blocking file read uses fs.readFile with a callback to handle data after reading.

2. Step 2: Check options for callback usage

   fs.readFile('file.txt', (err, data) => { if (err) throw err; console.log(data); }); uses fs.readFile with a callback function correctly handling error and data.

3. Final Answer:

   fs.readFile('file.txt', (err, data) => { if (err) throw err; console.log(data); }); -> Option A

4. Quick Check:

   Non-blocking file read uses callback = fs.readFile('file.txt', (err, data) => { if (err) throw err; console.log(data); }); [OK]

Hint: Non-blocking uses callbacks, blocking uses sync functions [OK]

Common Mistakes:

• Using synchronous readFileSync for non-blocking tasks
• Calling readFile without a callback
• Expecting immediate data return from async calls

3. What will the following Node.js code output?

console.log('Start');
setTimeout(() => { console.log('Timeout done'); }, 0);
console.log('End');

medium

A. Start\nEnd\nTimeout done

B. End\nStart\nTimeout done

C. Timeout done\nStart\nEnd

D. Start\nTimeout done\nEnd

Solution

1. Step 1: Understand synchronous logs

   console.log('Start') runs immediately and prints 'Start'.

2. Step 2: Understand setTimeout with 0 delay

   setTimeout callback runs after current code finishes, so 'Timeout done' prints last.

3. Step 3: Understand console.log('End')

   This runs immediately after 'Start', printing 'End' before the timeout callback.

4. Final Answer:

   Start End Timeout done -> Option A

5. Quick Check:

   Sync logs first, then async callback = Start\nEnd\nTimeout done [OK]

Hint: setTimeout with 0ms runs after current code finishes [OK]

Common Mistakes:

• Assuming setTimeout runs immediately
• Mixing order of synchronous and asynchronous logs
• Thinking 0ms delay means instant execution

4. Identify the error in this Node.js code snippet using non-blocking I/O:

const fs = require('fs');
let content;
fs.readFile('data.txt', (err, data) => {
  if (err) throw err;
  content = data.toString();
});
console.log(content);

medium

A. The callback function is missing the error parameter.

B. The readFile method should be readFileSync for async code.

C. The variable content is logged before the file read completes.

D. The data.toString() call is invalid.

Solution

1. Step 1: Understand async callback timing

   readFile runs asynchronously, so the callback runs after console.log(content).

2. Step 2: Check when content is logged

   console.log(content) runs immediately, before content is assigned inside the callback.

3. Final Answer:

   The variable content is logged before the file read completes. -> Option C

4. Quick Check:

   Async callback runs later, so content is undefined at log [OK]

Hint: Async callbacks run later; log inside callback to see data [OK]

Common Mistakes:

• Logging async data before callback runs
• Confusing sync and async readFile methods
• Ignoring error parameter in callback

5. You want to read two files in Node.js and then combine their contents. Which approach correctly uses non-blocking I/O to do this?

hard

A. Use fs.readFile once and then read the second file inside the first callback synchronously.

B. Use fs.readFileSync twice and then combine results synchronously.

C. Call fs.readFile twice with callbacks, combine results immediately after calling both without waiting.

D. Call fs.readFile twice with callbacks, combine results inside the second callback only after both finish.

Solution

1. Step 1: Understand non-blocking file reads

   Each fs.readFile runs asynchronously and needs a callback to get data.

2. Step 2: Combine results after both reads finish

   To combine contents, wait for both callbacks to complete, then combine inside the second callback or use coordination logic.

3. Final Answer:

   Call fs.readFile twice with callbacks, combine results inside the second callback only after both finish. -> Option D

4. Quick Check:

   Combine after both async reads finish = Call fs.readFile twice with callbacks, combine results inside the second callback only after both finish. [OK]

Hint: Combine data only after both async callbacks complete [OK]

Common Mistakes:

• Combining data before async reads finish
• Using synchronous reads in async code
• Nesting sync reads inside async callbacks incorrectly