Change stream events (insert, update, delete) in MongoDB - Step-by-Step Execution

Concept Flow - Change stream events (insert, update, delete)

Start watching collection

↓

Wait for event

↓

Event occurs?

No→Keep waiting

Yes↓

Identify event type

↓

Process

↓

Insert

↓

Continue watching

The system watches a collection and waits for changes. When an insert, update, or delete happens, it processes that event and keeps watching.

Execution Sample

MongoDB

const changeStream = collection.watch();
changeStream.on('change', (event) => {
  console.log(event.operationType);
});

This code listens for any change events on a MongoDB collection and prints the type of operation (insert, update, delete) when it happens.

Execution Table

Step	Event Occurs	operationType	Action Taken	Output
1	Insert document	insert	Log 'insert'	insert
2	Update document	update	Log 'update'	update
3	Delete document	delete	Log 'delete'	delete
4	No event	N/A	Wait for event	No output

💡 Watching continues indefinitely until stopped manually.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
event.operationType	undefined	insert	update	delete	undefined

Key Moments - 3 Insights

Why does the listener keep running even when no events happen?

Because the change stream waits for events asynchronously and does not stop unless explicitly closed, as shown in execution_table row 4.

What does 'operationType' represent in the event?

'operationType' tells what kind of change happened (insert, update, delete), as seen in execution_table rows 1-3.

Can multiple event types be handled in the same listener?

Yes, the listener checks the 'operationType' for each event and processes accordingly, demonstrated by the branching in concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the 'operationType' at Step 2?

A insert

B update

C delete

D N/A

💡 Hint

Check the 'operationType' column in execution_table row 2.

At which step does the system wait without output?

A Step 4

B Step 2

C Step 1

D Step 3

💡 Hint

Look for 'No event' and 'No output' in execution_table.

If a new 'replace' event type is added, how would the execution_table change?

A No change needed

B Replace 'delete' row with 'replace'

C Add a new row with operationType 'replace' and action to log 'replace'

D Remove 'insert' row

💡 Hint

Refer to how insert, update, and delete events are handled in execution_table rows 1-3.

Concept Snapshot

MongoDB change streams watch collections for changes.
Events include insert, update, and delete.
Each event has an 'operationType' field.
Listeners react to events asynchronously.
Change streams run until closed.

Full Transcript

This visual execution shows how MongoDB change streams work by watching a collection for changes. The flow starts by opening a watch on the collection, then waiting for events. When an event occurs, the system checks the type: insert, update, or delete. It processes the event accordingly, for example by logging the operation type. The listener keeps running and waiting for new events until it is stopped manually. Variables like 'event.operationType' change with each event, showing the current event type. Key moments include understanding that the listener runs continuously, what 'operationType' means, and that multiple event types can be handled in one listener. The quiz tests understanding of event types at specific steps, when the system waits, and how to add new event types.