Event loop mental model in Node.js

Introduction

The event loop helps Node.js handle many tasks without waiting for each to finish. It keeps your app fast and responsive.

When you want to run multiple tasks without blocking the program.

When handling user requests in a web server.

When working with timers or waiting for files to load.

When you want to run code after a delay or when an event happens.

When managing asynchronous operations like reading data from a database.

Syntax

Node.js

Node.js runs JavaScript code in a single thread.
The event loop checks for tasks to run and executes them one by one.
It handles callbacks from timers, I/O, and promises.

The event loop runs continuously while your program is active.

It uses queues to manage different types of tasks.

Examples

This shows how a timer callback waits 1 second before running, while the rest runs immediately.

Node.js

setTimeout(() => {
  console.log('Timer done');
}, 1000);

console.log('Start');

process.nextTick runs its callback before other queued tasks, right after the current code.

Node.js

console.log('First');
process.nextTick(() => {
  console.log('Next Tick');
});
console.log('Last');

Promise callbacks run after the current code but before timers, showing microtask queue behavior.

Node.js

Promise.resolve().then(() => {
  console.log('Promise resolved');
});
console.log('After promise');

Sample Program

This program shows the event loop order: synchronous code runs first, then promise callbacks, then timer callbacks.

Node.js

console.log('Start');

setTimeout(() => {
  console.log('Timeout callback');
}, 0);

Promise.resolve().then(() => {
  console.log('Promise callback');
});

console.log('End');

Important Notes

The event loop lets Node.js do many things without waiting for each to finish.

Microtasks like promises run before timers in the event loop.

Understanding the event loop helps avoid bugs with timing and order of code execution.

Summary

The event loop runs tasks in order to keep Node.js fast and non-blocking.

Synchronous code runs first, then microtasks like promises, then timers and I/O callbacks.

Knowing this helps you write better asynchronous code.

Practice

1. Which part of the Node.js event loop runs Promise callbacks before timers?

easy

A. I/O callbacks phase

B. Timers phase

C. Microtasks queue

D. Check phase

Solution

1. Step 1: Understand event loop phases

   The event loop has phases: timers, I/O callbacks, idle, poll, check, close callbacks, and microtasks run between phases.

2. Step 2: Identify when Promise callbacks run

   Promise callbacks are microtasks and run immediately after the current operation, before timers and I/O callbacks.

3. Final Answer:

   Microtasks queue -> Option C

4. Quick Check:

   Promises run in microtasks before timers [OK]

Hint: Remember: promises run before timers in microtasks [OK]

Common Mistakes:

• Thinking timers run before promises
• Confusing I/O callbacks with microtasks
• Assuming check phase runs before microtasks

2. Which of the following is the correct syntax to schedule a function to run after 0 milliseconds in Node.js?

easy

A. setTimeout(myFunc, 0);

B. setInterval(myFunc, 0);

C. process.nextTick(myFunc);

D. setImmediate(myFunc, 0);

Solution

1. Step 1: Identify function to run after delay

   setTimeout schedules a function after a specified delay in milliseconds.

2. Step 2: Check syntax for zero delay

   Using setTimeout(myFunc, 0) runs myFunc after the current call stack is empty, effectively scheduling it soon.

3. Final Answer:

   setTimeout(myFunc, 0); -> Option A

4. Quick Check:

   setTimeout with 0 delay schedules function correctly [OK]

Hint: Use setTimeout(func, 0) to schedule next tick [OK]

Common Mistakes:

• Using setInterval for one-time delay
• Passing extra argument to setImmediate
• Confusing process.nextTick with setTimeout syntax

3. What will be the output order of the following code?

console.log('start');
setTimeout(() => console.log('timeout'), 0);
Promise.resolve().then(() => console.log('promise'));
console.log('end');

medium

A. promisestartendtimeout

B. startpromiseendtimeout

C. startendtimeoutpromise

D. startendpromisetimeout

Solution

1. Step 1: Identify synchronous and asynchronous parts

   console.log('start') and console.log('end') run immediately (synchronously). setTimeout callback runs later. Promise callback runs as microtask after current stack.

2. Step 2: Trace execution order

   Output order: 'start' (sync), 'end' (sync), 'promise' (microtask), 'timeout' (timer callback).

3. Final Answer:

   start
   end
   promise
   timeout -> Option D

4. Quick Check:

   Synchronous > microtasks > timers [OK]

Hint: Sync logs first, then promises, then timers [OK]

Common Mistakes:

• Thinking promise runs after timeout
• Mixing order of synchronous logs
• Assuming setTimeout runs immediately

4. Consider this code snippet:

setTimeout(() => console.log('timeout'));
process.nextTick(() => console.log('nextTick'));
Promise.resolve().then(() => console.log('promise'));

Which line causes the earliest callback to run, and why might the output order be unexpected?

medium

A. process.nextTick runs earliest because it runs before microtasks

B. setTimeout runs earliest because timers run first

C. Promise.then runs earliest because promises run before nextTick

D. All callbacks run simultaneously

Solution

1. Step 1: Understand callback priorities

   process.nextTick callbacks run immediately after the current operation, before promise microtasks and timers.

2. Step 2: Explain output order

   Even though promises are microtasks, process.nextTick callbacks have higher priority and run first, which can surprise learners expecting promises first.

3. Final Answer:

   process.nextTick runs earliest because it runs before microtasks -> Option A

4. Quick Check:

   nextTick > promises > timers [OK]

Hint: nextTick runs before promises and timers [OK]

Common Mistakes:

• Assuming timers run before nextTick
• Confusing promise and nextTick order
• Thinking callbacks run simultaneously

5. You want to run a CPU-heavy task without blocking the event loop in Node.js. Which approach best uses the event loop model to keep your app responsive?

hard

A. Run the task synchronously in the main thread

B. Use setTimeout to split the task into smaller chunks

C. Use process.nextTick to run the entire task immediately

D. Run the task inside a Promise without splitting

Solution

1. Step 1: Understand event loop blocking

   Running a heavy task synchronously blocks the event loop, making the app unresponsive.

2. Step 2: Choose non-blocking approach

   Splitting the task into smaller chunks with setTimeout allows the event loop to process other events between chunks, keeping responsiveness.

3. Final Answer:

   Use setTimeout to split the task into smaller chunks -> Option B

4. Quick Check:

   Split heavy tasks with timers to avoid blocking [OK]

Hint: Split heavy tasks with setTimeout to avoid blocking [OK]

Common Mistakes:

• Running heavy tasks synchronously
• Using nextTick for long tasks (blocks event loop)
• Assuming promises alone prevent blocking