Events vs callbacks decision in Node.js - Visual Side-by-Side Comparison

Concept Flow - Events vs callbacks decision

Start Operation

↓

Choose: Use Callback?

Yes→Call callback when done

↓

Operation ends

↓

Use Event Emitter

↓

Emit event when done

↓

Listeners react to event

↓

Operation ends

This flow shows deciding between using a callback function or an event emitter to handle asynchronous operation completion.

Execution Sample

Node.js

const EventEmitter = require('events');
const emitter = new EventEmitter();

function doTask(callback) {
  setTimeout(() => {
    callback('done');
  }, 100);
}

doTask(result => console.log(result));

This code runs a task and uses a callback to print 'done' after 100ms.

Execution Table

Step	Action	Evaluation	Result
1	Call doTask with callback	doTask starts	Waiting 100ms
2	Timeout completes	Callback invoked with 'done'	Callback runs console.log('done')
3	console.log executes	Prints 'done' to console	Output: done
4	doTask ends	No more actions	Operation complete

💡 Callback called after timeout, operation completes

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
callback	function	function passed to doTask	function called with 'done'	function executed	no longer used
result	undefined	undefined	'done'	'done'	'done'

Key Moments - 2 Insights

Why does the callback run only after the timeout?

Because setTimeout delays calling the callback until 100ms pass, as shown in execution_table step 2.

How is the event approach different from the callback here?

Instead of passing a callback, the event approach emits an event that listeners respond to, allowing multiple reactions, unlike a single callback.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output at step 3?

A undefined

B 'done'

C Error

D null

💡 Hint

Check the 'Result' column in step 3 of execution_table.

At which step does the callback get called?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' and 'Evaluation' columns in execution_table for when callback is invoked.

If we switch to events, what changes in handling the operation completion?

A Multiple listeners can react to the event

B Callback function is called multiple times automatically

C Operation becomes synchronous

D No output is produced

💡 Hint

Refer to concept_flow where event listeners respond to emitted events.

Concept Snapshot

Events vs Callbacks decision in Node.js:
- Callback: pass a function to run once async task finishes
- Event: emit named events, multiple listeners can react
- Use callback for simple single response
- Use events for multiple reactions or decoupled design
- Both handle async completion but differ in flexibility

Full Transcript

This lesson shows how Node.js handles asynchronous operations using callbacks or events. When using a callback, you pass a function to be called once the task finishes, like after a timeout. The callback runs once and handles the result directly. Alternatively, using events involves emitting an event when the task completes. Multiple listeners can then respond to this event independently. The flow diagram shows choosing between these two methods. The execution table traces a callback example step-by-step, showing when the callback is called and the output printed. Variable tracking shows how the callback function and result change over time. Key moments clarify why the callback runs after the timeout and how events differ by allowing multiple listeners. The quiz tests understanding of output timing, callback invocation, and event benefits. This helps beginners see the practical difference between callbacks and events in Node.js.

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