Change streams on databases in MongoDB - Time & Space Complexity

Time Complexity: Change streams on databases

O(n)

Understanding Time Complexity

When using change streams in MongoDB, it's important to understand how the time to process changes grows as more changes happen.

We want to know how the cost of watching and reacting to database changes scales with the number of changes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

const changeStream = db.collection('orders').watch();
changeStream.on('change', (change) => {
  // Process each change event
  console.log(change);
});
    

This code listens for changes on the 'orders' collection and processes each change as it arrives.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Processing each change event as it arrives.
• How many times: Once per change event, repeating indefinitely as changes occur.

How Execution Grows With Input

Each new change event triggers one processing operation.

Input Size (n)	Approx. Operations
10	10 processing calls
100	100 processing calls
1000	1000 processing calls

Pattern observation: The number of operations grows directly with the number of changes.

Final Time Complexity

Time Complexity: O(n)

This means the time to process changes grows linearly with the number of change events.

Common Mistake

[X] Wrong: "Change streams process all changes instantly regardless of how many there are."

[OK] Correct: Each change event requires processing time, so more changes mean more work and longer total processing time.

Interview Connect

Understanding how change streams scale helps you explain real-time data handling and event-driven designs clearly and confidently.

Self-Check

"What if we added filtering to the change stream to only process certain changes? How would the time complexity change?"

Practice

1. What is the main purpose of MongoDB change streams on databases?

easy

A. To listen for real-time changes in the database

B. To backup the database automatically

C. To create indexes on collections

D. To run queries faster

Solution

1. Step 1: Understand what change streams do

   Change streams allow applications to watch for changes like inserts, updates, or deletes in real-time.

2. Step 2: Compare options with this purpose

   Only To listen for real-time changes in the database describes listening to real-time changes, which matches the main purpose of change streams.

3. Final Answer:

   To listen for real-time changes in the database -> Option A

4. Quick Check:

   Change streams = real-time listening [OK]

Hint: Change streams = real-time database updates listener [OK]

Common Mistakes:

• Confusing change streams with backups
• Thinking change streams create indexes
• Assuming change streams speed up queries

2. Which of the following is the correct syntax to start watching changes on a MongoDB database named mydb?

easy

A. watch.db('mydb')

B. db.watch('mydb')

C. db.mydb.watch()

D. db.getSiblingDB('mydb').watch()

Solution

1. Step 1: Recall how to access a database in MongoDB shell

   To access a database other than the current one, use db.getSiblingDB('mydb').

2. Step 2: Apply the watch() method on the database object

   The watch() method is called on the database object to start change streams.

3. Final Answer:

   db.getSiblingDB('mydb').watch() -> Option D

4. Quick Check:

   Use getSiblingDB to access db, then watch() [OK]

Hint: Use db.getSiblingDB('name').watch() to watch a database [OK]

Common Mistakes:

• Trying to call watch() directly on db with database name
• Using incorrect method like db.watch('name')
• Confusing method order or syntax

3. Given the following code snippet, what will be the output if a document is inserted into any collection in the testdb database?

const changeStream = db.getSiblingDB('testdb').watch();
changeStream.forEach((change) => {
  printjson(change.operationType);
});

medium

A. "update"

B. "delete"

C. "insert"

D. No output

Solution

1. Step 1: Understand what triggers the change event

   The change stream listens to all changes in the database, including inserts, updates, and deletes.

2. Step 2: Identify the operationType for an insert

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

3. Final Answer:

   "insert" -> Option C

4. Quick Check:

   Insert triggers operationType = "insert" [OK]

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

Common Mistakes:

• Expecting 'update' or 'delete' for insert events
• Thinking no output occurs without filters
• Confusing event names with method names

4. Identify the error in this code snippet that tries to watch changes on the sales database:

const changeStream = db.sales.watch();
changeStream.forEach((change) => {
  printjson(change);
});

medium

A. The watch() method cannot be called on a database object

B. The database should be accessed using getSiblingDB('sales') before calling watch()

C. The on() method is not valid for change streams

D. Missing parentheses after watch

Solution

1. Step 1: Check how the database is accessed

   Using db.sales accesses a collection named 'sales' in the current database, not the database itself.

2. Step 2: Correct way to access a different database

   To watch changes on the 'sales' database, use db.getSiblingDB('sales').watch().

3. Final Answer:

   The database should be accessed using getSiblingDB('sales') before calling watch() -> Option B

4. Quick Check:

   Use getSiblingDB to access database, not db.sales [OK]

Hint: Use getSiblingDB('name') to access database, not db.name [OK]

Common Mistakes:

• Assuming db.sales is a database instead of a collection
• Thinking watch() can't be called on database objects
• Confusing event handling methods

5. You want to watch only update operations on the orders database using change streams. Which code snippet correctly applies a filter to achieve this?

hard

A. db.getSiblingDB('orders').watch([{ $match: { operationType: 'update' } }])

B. db.orders.watch({ operationType: 'update' })

C. db.getSiblingDB('orders').watch({ filter: { operationType: 'update' } })

D. db.getSiblingDB('orders').watch([{ $filter: { operationType: 'update' } }])

Solution

1. Step 1: Recall how to filter change streams

   Change streams accept an aggregation pipeline array to filter events, using stages like $match.

2. Step 2: Apply correct syntax for filtering updates

   The correct filter is [{ $match: { operationType: 'update' } }] passed as an array to watch().

3. Final Answer:

   db.getSiblingDB('orders').watch([{ $match: { operationType: 'update' } }]) -> Option A

4. Quick Check:

   Use $match in array to filter change streams [OK]

Hint: Use watch([{ $match: { operationType: 'update' } }]) to filter updates [OK]

Common Mistakes:

• Passing filter as object instead of pipeline array
• Using invalid keys like 'filter' or '$filter'
• Calling watch() on collection instead of database