Event-driven architecture in Express - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the EventEmitter class from the 'events' module.

Express

const [1] = require('events');

Drag options to blanks, or click blank then click option'

AEmitterClass

BEventEmitter

CEmitter

DEvent

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect class names like 'Emitter' or 'Event'.

Forgetting to import from 'events' module.

The EventEmitter class is imported from the 'events' module to create event-driven behavior.

2fill in blank

medium

Complete the code to create a new instance of EventEmitter.

Express

const emitter = new [1]();

Drag options to blanks, or click blank then click option'

AEventEmitter

BEmitter

CEvent

DEventClass

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect class names like 'Emitter' or 'Event'.

Forgetting the parentheses to create an instance.

You create a new event emitter by calling new EventEmitter().

3fill in blank

hard

Fix the error in the code to listen for the 'start' event.

Express

emitter.[1]('start', () => {
  console.log('Started');
});

Drag options to blanks, or click blank then click option'

Alisten

BonStart

Con

DaddListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'listen' or 'onStart'.

Confusing event registration with event emitting.

The correct method to listen for events is on. It registers a callback for the event.

4fill in blank

hard

Fill both blanks to emit a 'data' event with a message.

Express

emitter.[1]('[2]', 'Hello World');

Drag options to blanks, or click blank then click option'

Aemit

Bon

Cdata

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'on' instead of 'emit' to trigger events.

Using wrong event names.

Use emit to trigger an event. The event name here is data.

5fill in blank

hard

Fill all three blanks to create an event listener that logs the received message.

Express

emitter.[1]('message', ([2]) => {
  console.log([3]);
});

Drag options to blanks, or click blank then click option'

Aon

Bmsg

Demit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'emit' instead of 'on' to listen.

Using different variable names inconsistently.

Use on to listen for 'message' events. The callback receives the message as msg and logs it.

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