Event-driven architecture in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is event-driven architecture in Express?

It is a design where the app reacts to events like user actions or messages by running specific code called event handlers.

intermediate

How does Express handle events internally?

Express uses Node.js's EventEmitter to listen for and respond to events like HTTP requests.

beginner

What is an event emitter in Express?

An event emitter is an object that sends out signals (events) that other parts of the app can listen to and react upon.

beginner

Why use event-driven architecture in web apps?

It helps apps respond quickly and efficiently to user actions or system changes without waiting, making apps more interactive and scalable.

intermediate

Give an example of an event-driven pattern in Express.

Using middleware functions that listen for HTTP request events and process them step-by-step is an event-driven pattern.

What does an event emitter do in Express?

A Handles CSS styling

B Stores data in a database

C Renders HTML pages

D Sends out events for other parts to listen to

Event emitters send out events that listeners can react to.

Which Node.js module is key for event-driven programming in Express?

A events

B http

C fs

D path

The 'events' module provides EventEmitter used in event-driven design.

What triggers event handlers in Express?

A CSS changes

B User actions or system events

C Database schema updates

D Image uploads only

Event handlers run when events like user clicks or requests happen.

Middleware in Express is an example of what architecture style?

A Event-driven

B Client-server

C Batch processing

D Monolithic

Middleware listens for request events and processes them stepwise.

Why is event-driven architecture good for scalability?

A It processes events one by one slowly

B It uses more memory

C It allows handling many events independently and quickly

D It requires less code comments

Handling events independently helps apps scale better.

Explain how event-driven architecture works in Express and why it is useful.

Think about how Express reacts to HTTP requests as events.

Describe the role of middleware in Express's event-driven architecture.

Middleware functions run in order when a request event happens.

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