Event-driven architecture in Express - Step-by-Step Execution

Concept Flow - Event-driven architecture

Event Occurs

↓

Event Emitted

↓

Event Listeners Check

↓

Listener 1

↓

Listener 1 Action

↓

Continue Program

When an event happens, it is emitted. Listeners waiting for that event react by running their actions.

Execution Sample

Express

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

emitter.on('greet', () => {
  console.log('Hello!');
});

emitter.emit('greet');

This code sets up a listener for a 'greet' event and then emits that event, causing the listener to run.

Execution Table

Step	Action	Event	Listeners Present	Listener Action	Output
1	Create EventEmitter instance	N/A	None yet	None	No output
2	Add listener for 'greet'	'greet'	1 listener added	Listener waits	No output
3	Emit 'greet' event	'greet'	1 listener active	Run listener callback	Prints 'Hello!'
4	No more events	N/A	Listeners remain	No action	Execution ends

💡 No more events emitted, program stops listening.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
emitter	undefined	EventEmitter instance	Same instance with listener	Same instance	Same instance
listeners for 'greet'	0	0	1 listener function	1 listener function	1 listener function

Key Moments - 2 Insights

Why does the listener run only after emit is called?

Listeners wait silently until the event is emitted (see Step 3 in execution_table). Emitting triggers all listeners for that event.

Can multiple listeners respond to the same event?

Yes, multiple listeners can be added and all run when the event is emitted (concept_flow shows branching to multiple listeners).

Visual Quiz - 3 Questions

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

A Prints 'Hello!'

B No output

C Error thrown

D Listener removed

💡 Hint

Check the 'Output' column at Step 3 in execution_table.

At which step is the listener added for the 'greet' event?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' and 'Listeners Present' columns in execution_table.

If we emit 'greet' twice, how would the output change?

A Prints 'Hello!' once

B Prints 'Hello!' twice

C No output

D Error on second emit

💡 Hint

Each emit triggers all listeners; see Step 3 behavior in execution_table.

Concept Snapshot

Event-driven architecture in Express:
- Create an EventEmitter instance
- Add listeners with .on(event, callback)
- Emit events with .emit(event)
- All listeners for that event run on emit
- Allows decoupled, asynchronous reactions to events

Full Transcript

Event-driven architecture means your program waits for events to happen, then reacts. In Express, you create an EventEmitter object. You add listeners that wait for named events. When you emit an event, all listeners for that event run their code. This lets your app respond to things like user actions or data arriving without blocking other work. The example code shows adding a listener for 'greet' and then emitting 'greet' to print 'Hello!'. Listeners only run when their event is emitted. You can have many listeners for the same event. Emitting multiple times runs listeners each time.