Use cases for change streams in MongoDB - Mini Project: Build & Apply

Use Cases for Change Streams in MongoDB

📖 Scenario: You are building a real-time notification system for an online store. You want to track changes in the orders collection to notify the sales team immediately when a new order is placed or an existing order is updated.

🎯 Goal: Create a MongoDB change stream to watch the orders collection for insert and update events, and prepare the system to handle these changes.

📋 What You'll Learn

Create a MongoDB collection named orders with sample documents.

Define a change stream on the orders collection.

Filter the change stream to listen only for insert and update operations.

Set up a basic handler to process the change events.

💡 Why This Matters

🌍 Real World

Change streams allow applications to react immediately to database changes, enabling real-time features like notifications, analytics, and synchronization.

💼 Career

Understanding change streams is valuable for backend developers, database administrators, and anyone building reactive or event-driven applications with MongoDB.

1

Create the orders collection with sample data

Create a MongoDB collection called orders and insert these exact documents: { _id: 1, item: "laptop", quantity: 2 } and { _id: 2, item: "phone", quantity: 5 }.

MongoDB

// Insert the sample documents into the orders collection
// Your code here

Hint

Use insertMany on db.orders with an array of the two documents.

2

Define a change stream on the orders collection

Create a variable called changeStream that watches the orders collection using db.orders.watch().

MongoDB

db.orders.insertMany([
  { _id: 1, item: "laptop", quantity: 2 },
  { _id: 2, item: "phone", quantity: 5 }
])

// Create a change stream on the orders collection
// Your code here

Hint

Use db.orders.watch() and assign it to changeStream.

3

Filter the change stream for insert and update events

Modify the changeStream to watch only for insert and update operations by passing a pipeline with $match on operationType equal to insert or update.

MongoDB

db.orders.insertMany([
  { _id: 1, item: "laptop", quantity: 2 },
  { _id: 2, item: "phone", quantity: 5 }
])

// Create a filtered change stream for insert and update
// Your code here

Hint

Pass an array with a $match stage to db.orders.watch() filtering operationType with $in.

4

Set up a handler to process change events

Add a listener to changeStream using changeStream.on('change', callback) where the callback receives a change object and logs the operationType and fullDocument fields.

MongoDB

db.orders.insertMany([
  { _id: 1, item: "laptop", quantity: 2 },
  { _id: 2, item: "phone", quantity: 5 }
])

const changeStream = db.orders.watch([
  { $match: { operationType: { $in: ["insert", "update"] } } }
], { fullDocument: "updateLookup" })

// Add a change event listener to changeStream
// Your code here

Hint

Use changeStream.on('change', callback) and inside the callback access change.operationType and change.fullDocument.

Practice

1. What is a primary use case for MongoDB change streams?

easy

A. To get real-time notifications when data changes in the database

B. To backup the entire database automatically

C. To create indexes on collections

D. To run complex aggregation queries

Solution

1. Step 1: Understand what change streams do

   Change streams allow applications to listen for changes in MongoDB collections or databases in real time.

2. Step 2: Identify the main use case

   This feature is mainly used to get notified instantly when data changes, enabling live updates or triggers.

3. Final Answer:

   To get real-time notifications when data changes in the database -> Option A

4. Quick Check:

   Change streams = real-time notifications [OK]

Hint: Change streams = instant reaction to data changes [OK]

Common Mistakes:

• Confusing change streams with backup tools
• Thinking change streams create indexes
• Assuming change streams run queries

2. Which of the following is the correct syntax to start a change stream on a collection named orders in MongoDB?

easy

A. db.orders.streamChanges()

B. db.orders.changeStream()

C. db.orders.listen()

D. db.orders.watch()

Solution

1. Step 1: Recall the MongoDB change stream method

   The correct method to open a change stream on a collection is watch().

2. Step 2: Match the method to the collection

   Calling db.orders.watch() starts watching changes on the orders collection.

3. Final Answer:

   db.orders.watch() -> Option D

4. Quick Check:

   Change stream method = watch() [OK]

Hint: Change streams start with .watch() on collections [OK]

Common Mistakes:

• Using non-existent methods like changeStream()
• Confusing with listen() or streamChanges()
• Missing parentheses after watch

3. Given the following code snippet, what will be the output when a new document is inserted into the products collection?

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

medium

A. Nothing will print because the listener is incorrect

B. "insert" will be printed to the console

C. An error will occur because watch requires parameters

D. "update" will be printed to the console

Solution

1. Step 1: Understand the change stream event listener

   The code listens for any change events on the products collection and logs the operationType.

2. Step 2: Identify the operation type for insert

   When a new document is inserted, the operationType is "insert".

3. Final Answer:

   "insert" will be printed to the console -> Option B

4. Quick Check:

   Insert triggers operationType = "insert" [OK]

Hint: Insert triggers operationType 'insert' in change stream [OK]

Common Mistakes:

• Thinking watch() needs parameters to work
• Confusing operationType values
• Assuming listener syntax is wrong

4. You wrote this code to watch changes on the users collection but it throws an error:

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

What is the likely cause of the error?

medium

A. The fullDocument option should be passed as the second argument to watch() after the pipeline array

B. The fullDocument option value should be 'updateLookup' without quotes

C. The watch method does not accept any options

D. The watch method requires a callback function as the first argument

Solution

1. Step 1: Review correct usage of watch options

   The watch method accepts an optional aggregation pipeline array as the first argument, and options as the second argument.

2. Step 2: Identify the mistake in option placement

   Passing { fullDocument: 'updateLookup' } directly as the first argument is incorrect; it should be the second argument after the pipeline array.

3. Final Answer:

   The fullDocument option should be passed as the second argument to watch() after the pipeline array -> Option A

4. Quick Check:

   Options go as second argument to watch() [OK]

Hint: Options are second argument in watch(), not first [OK]

Common Mistakes:

• Passing options as first argument instead of second
• Removing quotes from string option values
• Expecting watch() to take a callback argument

5. You want to build a live dashboard that updates instantly when orders are inserted or updated in the orders collection. Which approach using change streams is best to minimize data transfer and improve performance?

hard

A. Poll the orders collection every 5 seconds instead of using change streams

B. Watch the entire orders collection without filters and send full documents on every change

C. Use a change stream with a pipeline to filter only insert and update operations and project only needed fields

D. Use change streams but ignore the update operations to reduce complexity

Solution

1. Step 1: Identify the goal for live dashboard updates

   The dashboard needs instant updates only for inserts and updates, not deletes or other operations.

2. Step 2: Choose efficient change stream usage

   Filtering the change stream with a pipeline to watch only insert and update operations and projecting only necessary fields reduces data sent and improves performance.

3. Final Answer:

   Use a change stream with a pipeline to filter only insert and update operations and project only needed fields -> Option C

4. Quick Check:

   Filter and project in change streams for efficiency [OK]

Hint: Filter and project in change streams to optimize data [OK]

Common Mistakes:

• Watching all changes without filters wastes bandwidth
• Polling is less efficient than change streams
• Ignoring updates misses important dashboard changes