Single-threaded non-blocking I/O concept in Node.js - Step-by-Step Execution

Concept Flow - Single-threaded non-blocking I/O concept

Start single thread

↓

Receive I/O request

↓

Start I/O operation asynchronously

↓

Continue running other code

↓

I/O operation completes

↓

Callback/event handler runs

↓

Process I/O result

↓

Loop back to wait for more events

The single thread starts an I/O operation without waiting, continues other work, and later handles the I/O result via a callback.

Execution Sample

Node.js

const fs = require('fs');
console.log('Start');
fs.readFile('file.txt', (err, data) => {
  console.log('File read');
});
console.log('End');

This code logs 'Start', starts reading a file asynchronously, logs 'End', then logs 'File read' when the file is done.

Execution Table

Step	Action	Output	Thread State	Callback Queue
1	Run console.log('Start')	'Start'	Running main thread	Empty
2	Call fs.readFile (async start)	No output	Starts async I/O	Empty
3	Run console.log('End')	'End'	Main thread continues	Empty
4	I/O completes	No output	Main thread idle or running other code	Callback for readFile queued
5	Process readFile callback	'File read'	Callback runs on main thread	Empty

💡 All code and callbacks processed, no more events to handle

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
Callback Queue	Empty	Empty	Contains readFile callback	Empty

Key Moments - 3 Insights

Why does 'End' print before 'File read' even though readFile is called first?

Because fs.readFile starts an asynchronous operation and does not block the thread. The main thread continues to run and prints 'End' before the file reading finishes and the callback runs (see steps 2 and 3 in execution_table).

Does Node.js use multiple threads to read the file?

No, the main JavaScript thread is single-threaded. The file reading happens asynchronously using system threads or the OS, but the JavaScript code runs on one thread. The callback runs back on the main thread (see thread state in steps 2 and 5).

What happens if the callback takes a long time to run?

Since the callback runs on the single main thread, it blocks other JavaScript code from running until it finishes. This can delay other events or callbacks (implied by the single-threaded nature in the concept_flow).

Visual Quiz - 3 Questions

Look at the execution_table, what is printed at Step 3?

A 'End'

B 'File read'

C 'Start'

D No output

💡 Hint

Check the Output column at Step 3 in the execution_table

At which step does the callback for reading the file get queued?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the Callback Queue column in the execution_table

If the callback took a long time to run, what would happen to the thread state at Step 5?

A Main thread would start a new thread for the callback

B Main thread would be blocked running the callback

C Main thread would run other callbacks simultaneously

D Main thread would pause and wait for I/O

💡 Hint

Refer to the key_moments explanation about single-threaded callback execution

Concept Snapshot

Single-threaded non-blocking I/O in Node.js:
- JavaScript runs on one thread.
- I/O operations start asynchronously and do not block.
- Main thread continues running other code.
- When I/O finishes, callback is queued.
- Callback runs on main thread, can block if long.
- Enables efficient handling of many I/O tasks.

Full Transcript

In Node.js, JavaScript runs on a single thread. When an I/O operation like reading a file is requested, Node.js starts it asynchronously without waiting. This means the main thread keeps running other code, like logging 'End'. When the I/O finishes, its callback is added to a queue. The main thread then runs this callback, printing 'File read'. This approach avoids blocking the thread during slow I/O, allowing efficient multitasking. However, since callbacks run on the single thread, long callbacks can block other code. This is the core of Node.js's single-threaded non-blocking I/O model.

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