Change streams on databases in MongoDB - Step-by-Step Execution

Concept Flow - Change streams on databases

Start watching database

↓

Database change occurs

↓

Change stream detects change

↓

Change event sent to client

↓

Client processes event

↓

Continue listening or stop

Change streams let you watch for changes in a MongoDB database and get notified when something changes.

Execution Sample

MongoDB

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

This code listens for any change in the database and prints the change details when it happens.

Execution Table

Step	Action	Change Detected?	Event Sent	Client Output
1	Start watching database with db.watch()	No	No	No output
2	Insert a document into a collection	Yes	Yes	{"operationType":"insert", "ns":{"db":"test", "coll":"users"}, "fullDocument":{...}}
3	Update a document in the collection	Yes	Yes	{"operationType":"update", "ns":{"db":"test", "coll":"users"}, "updateDescription":{...}}
4	Delete a document from the collection	Yes	Yes	{"operationType":"delete", "ns":{"db":"test", "coll":"users"}, "documentKey":{...}}
5	No further changes	No	No	No output

💡 Listening stops when client closes the change stream or application ends.

Variable Tracker

Variable	Start	After Insert	After Update	After Delete	Final
changeStream.isOpen	true	true	true	true	false
changeStream.latestEvent	null	{"operationType":"insert"}	{"operationType":"update"}	{"operationType":"delete"}	null

Key Moments - 3 Insights

Why does the change stream not output anything before any database change?

Because the change stream only sends events when a change happens, as shown in execution_table step 1 where no change means no output.

What happens if multiple changes occur quickly?

Each change triggers a separate event sent to the client, so the client receives multiple change events in order, as seen in steps 2, 3, and 4.

Does the change stream keep running forever?

No, it runs until the client closes it or the application stops, as noted in the exit_note.

Visual Quiz - 3 Questions

Look at the execution_table, what is the client output at step 3?

A No output

B {"operationType":"update", "ns":{"db":"test", "coll":"users"}, "updateDescription":{...}}

C {"operationType":"insert", "ns":{"db":"test", "coll":"users"}, "fullDocument":{...}}

D {"operationType":"delete", "ns":{"db":"test", "coll":"users"}, "documentKey":{...}}

💡 Hint

Check the 'Client Output' column at step 3 in the execution_table.

According to variable_tracker, what is the value of changeStream.isOpen after the delete operation?

A false

B null

C true

D undefined

💡 Hint

Look at the 'After Delete' column for changeStream.isOpen in variable_tracker.

If no changes happen after starting the change stream, what will the client see?

A No output

B Continuous change events

C An error message

D A snapshot of the database

💡 Hint

Refer to step 1 and 5 in execution_table where no changes mean no output.

Concept Snapshot

Change streams let you watch MongoDB databases for changes.
Use db.watch() to start listening.
Events like insert, update, delete trigger notifications.
Client receives change events in real time.
Stop listening by closing the stream.

Full Transcript

Change streams in MongoDB allow applications to listen for changes in the database. When you start a change stream using db.watch(), it waits for any changes like inserts, updates, or deletes. When a change happens, the stream sends an event to the client with details about the change. The client can then process this event, for example, by logging it or updating a UI. The stream keeps running until the client closes it or the application ends. If no changes happen, no events are sent. This lets applications react immediately to database changes without polling.