Events vs callbacks decision in Node.js - Hands-On Comparison

Events vs Callbacks Decision in Node.js

📖 Scenario: You are building a simple Node.js program that simulates a download process. You want to learn how to handle the completion of the download using two common ways: callbacks and events.This will help you understand when to use callbacks and when to use events in Node.js.

🎯 Goal: Create a Node.js script that first uses a callback to notify when a download finishes, then refactor it to use an event emitter to notify the same.This will show you the difference between callbacks and events and when each is useful.

📋 What You'll Learn

Create a function called downloadFile that accepts a callback function

Call the callback function after simulating a download delay

Create an EventEmitter instance called downloader

Emit a done event after simulating the download delay

Listen to the done event and log a message

💡 Why This Matters

🌍 Real World

Handling asynchronous operations like file downloads, user actions, or server responses in Node.js applications.

💼 Career

Understanding callbacks and events is essential for Node.js developers to write clean, maintainable, and scalable asynchronous code.

1

Create the download function with a callback

Create a function called downloadFile that takes a callback parameter. Inside it, use setTimeout to simulate a 1 second delay, then call the callback function.

Node.js

# Create the downloadFile function with a callback
# Your code here

Hint

Use setTimeout to simulate delay and call the callback inside it.

2

Call downloadFile with a callback to log completion

Call the downloadFile function and pass a callback function that logs 'Download complete using callback'.

Node.js

function downloadFile(callback) {
    setTimeout(() => {
        callback();
    }, 1000);
}

// Call downloadFile with a callback
# Your code here

Hint

Pass an arrow function to downloadFile that logs the message.

3

Create an EventEmitter and emit 'done' event after delay

Import EventEmitter from 'events'. Create a constant called downloader as a new EventEmitter. Create a function called downloadFileEvent that uses setTimeout to emit a 'done' event on downloader after 1 second.

Node.js

function downloadFile(callback) {
    setTimeout(() => {
        callback();
    }, 1000);
}

downloadFile(() => {
    console.log('Download complete using callback');
});

// Import EventEmitter and create downloader
// Create downloadFileEvent function
# Your code here

Hint

Use require('events') to import EventEmitter and create an instance.

4

Listen to 'done' event and call downloadFileEvent

Add a listener on downloader for the 'done' event that logs 'Download complete using event'. Then call the downloadFileEvent function.

Node.js

const EventEmitter = require('events');

function downloadFile(callback) {
    setTimeout(() => {
        callback();
    }, 1000);
}

downloadFile(() => {
    console.log('Download complete using callback');
});

const downloader = new EventEmitter();

function downloadFileEvent() {
    setTimeout(() => {
        downloader.emit('done');
    }, 1000);
}

// Listen to 'done' event and log message
// Call downloadFileEvent
# Your code here

Hint

Use downloader.on('done', callback) to listen for the event.

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