Events vs callbacks decision in Node.js - Performance Comparison

Performance: Events vs callbacks decision

MEDIUM IMPACT

This concept affects how asynchronous operations impact responsiveness and CPU usage in Node.js applications.

Handling multiple asynchronous operations with different outcomes

Node.js

const EventEmitter = require('events');
class DataFetcher extends EventEmitter {
  fetch() {
    database.query('SELECT * FROM table', (err, result) => {
      if (err) return this.emit('error', err);
      this.emit('data', result);
    });
  }
}
const fetcher = new DataFetcher();
fetcher.on('data', (result) => {
  processData(result, (err, processed) => {
    if (err) return fetcher.emit('error', err);
    fetcher.emit('done', processed);
  });
});

Events decouple steps, avoid deep nesting, and allow better asynchronous flow control.

📈 Performance GainImproves INP by reducing callback blocking and enabling parallel event handling.

Handling multiple asynchronous operations with different outcomes

Node.js

function fetchData(callback) {
  database.query('SELECT * FROM table', (err, result) => {
    if (err) return callback(err);
    processData(result, (err, processed) => {
      if (err) return callback(err);
      callback(null, processed);
    });
  });
}

Callback nesting leads to harder-to-read code and potential blocking if callbacks are heavy.

📉 Performance CostBlocks event loop briefly during nested callbacks; harder to optimize for responsiveness.

Performance Comparison

Pattern	Callback Nesting	Event Loop Blocking	Code Complexity	Verdict
Callbacks with nesting	High (deep nesting)	Medium (blocking during callbacks)	High (hard to maintain)	[X] Bad
Event-driven with emitters	Low (flat event handlers)	Low (non-blocking event dispatch)	Low (clear separation)	[OK] Good

Rendering Pipeline

In Node.js, event-driven architecture processes events asynchronously, allowing the event loop to remain free for other tasks, improving responsiveness.

→Event Loop

→Callback Execution

→Task Scheduling

⚠️ BottleneckCallback Execution when callbacks are nested or blocking

Core Web Vital Affected

INP

This concept affects how asynchronous operations impact responsiveness and CPU usage in Node.js applications.

Optimization Tips

1Avoid deep callback nesting to keep the event loop responsive.

2Use event emitters to decouple asynchronous logic and improve maintainability.

3Monitor event loop blocking to ensure smooth input responsiveness.

Performance Quiz - 3 Questions

Which pattern generally improves Node.js responsiveness by avoiding deep callback nesting?

A Using nested callbacks for sequential operations

B Using event emitters to handle asynchronous steps

C Blocking the event loop with synchronous code

D Using setTimeout to delay callbacks

DevTools: Performance

How to check: Record a CPU profile while running asynchronous code; look for long callback stacks and event loop delays.

What to look for: Long blocking times in callback execution indicate callback nesting issues; smooth event dispatch shows good event-driven design.

Practice

1. Which statement best describes when to use callbacks versus events in Node.js?

easy

A. Use callbacks for simple single responses and events for multiple listeners.

B. Use events only for synchronous code and callbacks for asynchronous code.

C. Callbacks are for error handling only, events are for all other tasks.

D. Events replace callbacks completely in modern Node.js.

Solution

1. Step 1: Understand callbacks and events roles

   Callbacks run one function after a task finishes, suitable for simple, single responses.

2. Step 2: Understand events usage

   Events allow many listeners to respond to named signals, useful for complex or multiple reactions.

3. Final Answer:

   Use callbacks for simple single responses and events for multiple listeners. -> Option A

4. Quick Check:

   Callbacks = single response, Events = multiple listeners [OK]

Hint: Callbacks = one response; events = many listeners [OK]

Common Mistakes:

• Thinking events are only for synchronous code
• Believing callbacks handle all errors exclusively
• Assuming events completely replace callbacks

2. Which of the following is the correct syntax to add an event listener in Node.js?

easy

A. emitter.listen('eventName', callbackFunction);

B. emitter.addListener('eventName' callbackFunction);

C. emitter.callback('eventName', callbackFunction);

D. emitter.on('eventName', callbackFunction);

Solution

1. Step 1: Recall Node.js event listener syntax

   The standard method to add an event listener is using emitter.on with event name and callback.

2. Step 2: Check each option for syntax correctness

   emitter.on('eventName', callbackFunction); uses correct syntax with parentheses and comma. emitter.addListener('eventName' callbackFunction); misses a comma. Options A and D use invalid method names.

3. Final Answer:

   emitter.on('eventName', callbackFunction); -> Option D

4. Quick Check:

   Correct event listener syntax = emitter.on(...) [OK]

Hint: Use emitter.on('event', callback) for events [OK]

Common Mistakes:

• Missing comma between arguments
• Using incorrect method names like listen or callback
• Confusing addListener syntax without comma

3. What will be the output of this Node.js code snippet?

const EventEmitter = require('events');
const emitter = new EventEmitter();
emitter.on('greet', () => console.log('Hello!'));
emitter.emit('greet');
emitter.emit('greet');

medium

A. Hello! printed once

B. No output

C. Hello! printed twice

D. Error thrown

Solution

1. Step 1: Understand event listener and emit behavior

   Each call to emitter.emit triggers all listeners for that event. Here, 'greet' event has one listener printing 'Hello!'.

2. Step 2: Count how many times emit is called

   emit('greet') is called twice, so the listener runs twice, printing 'Hello!' two times.

3. Final Answer:

   Hello! printed twice -> Option C

4. Quick Check:

   emit triggers listeners each time = output twice [OK]

Hint: emit calls listeners every time it's invoked [OK]

Common Mistakes:

• Thinking emit triggers listener only once
• Expecting no output without callback arguments
• Confusing event registration with callback invocation

4. Identify the error in this Node.js code using callbacks and events:

const EventEmitter = require('events');
const emitter = new EventEmitter();
function task(callback) {
  emitter.emit('done');
  callback();
}
task(() => console.log('Callback finished'));
emitter.on('done', () => console.log('Event done'));

medium

A. The event listener is added after task is called, so event may be missed.

B. Callback should be called before emitting the event.

C. setTimeout is used incorrectly without delay argument.

D. EventEmitter cannot be used with callbacks.

Solution

1. Step 1: Check order of event listener and task call

   The event listener is added after task() is called, so the 'done' event may emit before listener exists.

2. Step 2: Understand event emission timing

   task emits 'done' synchronously when called, but listener is added after task() call, so emit happens before listener setup.

3. Final Answer:

   The event listener is added after task is called, so event may be missed. -> Option A

4. Quick Check:

   Listener must be added before event emit [OK]

Hint: Add event listeners before emitting events [OK]

Common Mistakes:

• Adding listeners after emitting events
• Confusing callback order with event order
• Assuming setTimeout needs no delay argument

5. You want to notify multiple parts of your Node.js app when a file download finishes, but also run a cleanup callback once. Which approach fits best?

hard

A. Use only events for everything including cleanup.

B. Use an event emitter to notify multiple listeners and a callback for cleanup after download.

C. Use multiple callbacks for each notification and cleanup.

D. Use only a callback for all notifications and cleanup.

Solution

1. Step 1: Analyze notification needs

   Multiple parts need to be notified, which fits event emitters allowing many listeners.

2. Step 2: Analyze cleanup requirement

   Cleanup runs once after download, suitable for a single callback after task completion.

3. Step 3: Combine approaches

   Use events for multiple notifications and a callback for single cleanup to keep code clear and efficient.

4. Final Answer:

   Use an event emitter to notify multiple listeners and a callback for cleanup after download. -> Option B

5. Quick Check:

   Events = multiple notifications, callback = single cleanup [OK]

Hint: Events for many, callback for one-time cleanup [OK]

Common Mistakes:

• Trying to use only callbacks for multiple notifications
• Using multiple callbacks instead of events
• Using events for single cleanup unnecessarily