Event-driven architecture in Express - Mini Project: Build & Apply

Building a Simple Event-Driven Server with Express

📖 Scenario: You are creating a small web server that reacts to events. This server will listen for HTTP requests and emit custom events when certain routes are accessed. This helps separate the logic of handling requests and responding to events.

🎯 Goal: Build an Express server that uses Node.js event-driven architecture. You will create an event emitter, set up a listener for a custom event, and trigger that event when a specific route is visited.

📋 What You'll Learn

Create an Express app instance

Create a Node.js EventEmitter instance

Set up an event listener for a custom event named userVisited

Emit the userVisited event when the /visit route is accessed

Send a response confirming the event was emitted

💡 Why This Matters

🌍 Real World

Event-driven architecture helps build scalable and maintainable servers by separating event handling from request processing.

💼 Career

Understanding event-driven patterns is essential for backend developers working with Node.js and Express to build responsive and modular applications.

1

Set up Express and EventEmitter

Create a constant called express that requires the 'express' module. Then create a constant called app by calling express(). Also, create a constant called EventEmitter that requires the 'events' module, and create a constant called eventEmitter by calling new EventEmitter().

Express

// Your code here

Hint

Use require('express') to import Express and require('events') to import the EventEmitter class.

2

Create a listener for the 'userVisited' event

Use eventEmitter.on to listen for the event named 'userVisited'. The listener should be a function that takes a username parameter and logs the message `User visited: ${username}` to the console.

Express

const express = require('express');
const app = express();
const EventEmitter = require('events');
const eventEmitter = new EventEmitter();

// Your code here

Hint

Use eventEmitter.on('userVisited', (username) => { ... }) to set up the listener.

3

Emit the 'userVisited' event on route access

Create a GET route on /visit using app.get. Inside the route handler, emit the 'userVisited' event on eventEmitter with the string 'Alice' as the username. Then send the response 'Welcome Alice!'.

Express

const express = require('express');
const app = express();
const EventEmitter = require('events');
const eventEmitter = new EventEmitter();

eventEmitter.on('userVisited', (username) => {
    console.log(`User visited: ${username}`);
});

// Your code here

Hint

Use app.get('/visit', (req, res) => { ... }) and inside call eventEmitter.emit('userVisited', 'Alice').

4

Start the Express server

Add app.listen to start the server on port 3000. The callback function should log 'Server running on port 3000' to the console.

Express

const express = require('express');
const app = express();
const EventEmitter = require('events');
const eventEmitter = new EventEmitter();

eventEmitter.on('userVisited', (username) => {
    console.log(`User visited: ${username}`);
});

app.get('/visit', (req, res) => {
    eventEmitter.emit('userVisited', 'Alice');
    res.send('Welcome Alice!');
});

// Your code here

Hint

Use app.listen(3000, () => { console.log('Server running on port 3000') }) to start the server.

Practice

1. What is the main purpose of using EventEmitter in an Express app?

easy

A. To allow the app to react to events asynchronously

B. To handle HTTP routing and middleware

C. To connect to a database

D. To serve static files

Solution

1. Step 1: Understand the role of EventEmitter

   EventEmitter is used to create and listen for events, enabling asynchronous reactions in the app.

2. Step 2: Compare with other Express features

   Routing, database connections, and static file serving are handled by other parts of Express, not EventEmitter.

3. Final Answer:

   To allow the app to react to events asynchronously -> Option A

4. Quick Check:

   EventEmitter = async event handling [OK]

Hint: EventEmitter means reacting to events, not routing or DB [OK]

Common Mistakes:

• Confusing EventEmitter with routing or middleware
• Thinking EventEmitter manages database connections
• Assuming EventEmitter serves static files

2. Which of the following is the correct way to create an event emitter in Express?

easy

A. const emitter = require('events').EventEmitter();

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

C. const emitter = new require('events');

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

Solution

1. Step 1: Recall correct import syntax

   The events module exports EventEmitter as a property, so you must access it before creating an instance.

2. Step 2: Check each option's syntax

   const EventEmitter = require('events').EventEmitter; const emitter = new EventEmitter(); correctly imports EventEmitter and creates a new instance. const EventEmitter = require('events'); const emitter = new EventEmitter(); misses the .EventEmitter property. Options A and C misuse the constructor call.

3. Final Answer:

   const EventEmitter = require('events').EventEmitter; const emitter = new EventEmitter(); -> Option B

4. Quick Check:

   Correct import and new instance = const EventEmitter = require('events').EventEmitter; const emitter = new EventEmitter(); [OK]

Hint: Remember to get EventEmitter from require('events').EventEmitter [OK]

Common Mistakes:

• Calling EventEmitter as a function without new
• Missing .EventEmitter when requiring events
• Using new with require() directly

3. What will be the output of this Express event-driven code?

const EventEmitter = require('events').EventEmitter;
const emitter = new EventEmitter();
emitter.on('greet', (name) => {
  console.log(`Hello, ${name}!`);
});
emitter.emit('greet', 'Alice');

medium

A. Hello, Alice!

B. greet Alice

C. Error: greet event not found

D. No output

Solution

1. Step 1: Understand event registration

   The code registers a listener for the 'greet' event that logs a greeting with the given name.

2. Step 2: Analyze event emission

   When emitter.emit('greet', 'Alice') runs, it triggers the listener, printing "Hello, Alice!".

3. Final Answer:

   Hello, Alice! -> Option A

4. Quick Check:

   Emit triggers listener output = Hello, Alice! [OK]

Hint: emit triggers on() listener with arguments [OK]

Common Mistakes:

• Expecting no output without console.log
• Confusing event name with output text
• Thinking emit returns a value

4. Identify the error in this Express event-driven code:

const EventEmitter = require('events').EventEmitter;
const emitter = new EventEmitter();
emitter.emit('start');
emitter.on('start', () => {
  console.log('Started');
});

medium

A. emit method does not exist

B. EventEmitter is not imported correctly

C. Listener callback syntax is invalid

D. The event listener is registered after the event is emitted

Solution

1. Step 1: Check event listener registration timing

   The listener for 'start' is added after emitter.emit('start') is called, so it misses the event.

2. Step 2: Verify other code parts

   Import and syntax are correct; emit exists and callback syntax is valid.

3. Final Answer:

   The event listener is registered after the event is emitted -> Option D

4. Quick Check:

   Listener must be before emit to catch event [OK]

Hint: Register listeners before emitting events [OK]

Common Mistakes:

• Emitting event before listener causes no output
• Assuming emit queues events for future listeners
• Misreading import or callback syntax

5. You want to build a real-time notification system in Express using event-driven architecture. Which approach best organizes your code for scalability?

hard

A. Create a single global EventEmitter instance and emit all events through it

B. Use only middleware functions without events for notifications

C. Create separate EventEmitter instances for different modules and communicate via events

D. Handle notifications by polling the database every second

Solution

1. Step 1: Consider modular event handling

   Using separate EventEmitter instances per module keeps code organized and decoupled, improving scalability.

2. Step 2: Evaluate other options

   A single global emitter can become a bottleneck. Middleware alone doesn't handle async events well. Polling is inefficient and not event-driven.

3. Final Answer:

   Create separate EventEmitter instances for different modules and communicate via events -> Option C

4. Quick Check:

   Modular emitters = scalable event-driven design [OK]

Hint: Use modular EventEmitters for clean, scalable code [OK]

Common Mistakes:

• Using one global emitter causing tight coupling
• Ignoring event-driven benefits by polling
• Relying only on middleware for async events