Why document databases over relational in MongoDB - Performance Analysis

Time Complexity: Why document databases over relational

O(1)

Understanding Time Complexity

We want to understand how the time it takes to work with data changes when using document databases compared to relational databases.

Specifically, we ask: How does the structure of data affect the speed of common operations?

Scenario Under Consideration

Analyze the time complexity of a simple MongoDB query that finds a document by its ID and updates a nested field.

// Find a user by ID and update their address city
const userId = ObjectId("12345");
db.users.updateOne(
  { _id: userId },
  { $set: { "address.city": "New City" } }
);
    

This code finds one user document by its unique ID and updates the city inside the nested address field.

Identify Repeating Operations

Look for repeated steps or loops in the operation.

• Primary operation: Searching for a document by its unique ID.
• How many times: This happens once per query, no loops over multiple documents.

How Execution Grows With Input

As the number of documents grows, finding by ID stays fast because of indexing.

Input Size (n)	Approx. Operations
10	Few operations, quick find
100	Still very few operations, quick find
1000	Still very few operations, quick find

Pattern observation: The time to find by ID does not grow much as data grows because indexes help keep it fast.

Final Time Complexity

Time Complexity: O(1)

This means the time to find and update a document by ID stays about the same no matter how many documents there are.

Common Mistake

[X] Wrong: "Finding a document by ID gets slower as the database grows because it has to check every document."

[OK] Correct: Document databases use indexes on IDs, so they jump directly to the right document without checking all others.

Interview Connect

Understanding how document databases handle queries efficiently shows you know how data structure and indexing affect speed. This skill helps you explain why certain databases fit some jobs better than others.

Self-Check

"What if we searched for a document by a field without an index? How would the time complexity change?"

Practice

1. Why might someone choose a document database like MongoDB over a traditional relational database?

easy

A. Because document databases store data in flexible JSON-like documents that can change structure easily.

B. Because document databases require fixed schemas and strict table relations.

C. Because document databases only work with numeric data.

D. Because document databases do not support indexing.

Solution

1. Step 1: Understand data storage formats

   Document databases store data as JSON-like documents, allowing flexible and dynamic structures.

2. Step 2: Compare with relational databases

   Relational databases require fixed schemas and tables, making changes harder.

3. Final Answer:

   Because document databases store data in flexible JSON-like documents that can change structure easily. -> Option A

4. Quick Check:

   Flexible JSON-like storage [OK]

Hint: Flexible JSON documents mean easier schema changes [OK]

Common Mistakes:

• Thinking document DBs require fixed schemas
• Believing document DBs only handle numbers
• Assuming no indexing in document DBs

2. Which of the following is the correct way to insert a document into a MongoDB collection named users?

easy

A. insert document into users {name: 'Alice', age: 30}

B. INSERT INTO users VALUES ('Alice', 30)

C. db.users.insertOne({name: 'Alice', age: 30})

D. db.users.add({name: 'Alice', age: 30})

Solution

1. Step 1: Recall MongoDB insert syntax

   MongoDB uses insertOne() to add a single document to a collection.

2. Step 2: Check options for correct syntax

   db.users.insertOne({name: 'Alice', age: 30}) uses db.users.insertOne({name: 'Alice', age: 30}), which is correct MongoDB syntax.

3. Final Answer:

   db.users.insertOne({name: 'Alice', age: 30}) -> Option C

4. Quick Check:

   MongoDB insertOne() [OK]

Hint: MongoDB uses insertOne() for single document inserts [OK]

Common Mistakes:

• Using SQL syntax in MongoDB
• Using non-existent methods like add()
• Writing commands as plain English

3. Given the following MongoDB document stored in the products collection:

{ "_id": 1, "name": "Pen", "details": { "color": "blue", "price": 1.5 } }

What will the query db.products.find({"details.color": "blue"}) return?

medium

A. All products with a details field containing color blue.

B. Only products with a top-level field named color equal to blue.

C. An error because nested fields cannot be queried.

D. No results because the query syntax is wrong.

Solution

1. Step 1: Understand dot notation in queries

   MongoDB allows querying nested fields using dot notation like "details.color".

2. Step 2: Analyze the query and document

   The document has a nested field details.color with value "blue", so the query matches this document.

3. Final Answer:

   All products with a details field containing color blue. -> Option A

4. Quick Check:

   Dot notation queries nested fields [OK]

Hint: Use dot notation to query nested document fields [OK]

Common Mistakes:

• Thinking nested fields can't be queried
• Confusing top-level and nested fields
• Assuming query syntax is SQL-like

4. You wrote this MongoDB query to find users aged over 25:

db.users.find({age: > 25})

Why does this query fail and how to fix it?

medium

A. Use SQL syntax: SELECT * FROM users WHERE age > 25.

B. The query is correct; failure is due to missing collection.

C. Replace > with >= for correct MongoDB syntax.

D. The operator > should be inside $gt like {age: {$gt: 25}}.

Solution

1. Step 1: Identify MongoDB comparison operator syntax

   MongoDB uses special operators like $gt for 'greater than' inside query objects.

2. Step 2: Correct the query syntax

   The correct query is {age: {$gt: 25}}, not using > directly.

3. Final Answer:

   The operator > should be inside $gt like {age: {$gt: 25}}. -> Option D

4. Quick Check:

   Use $gt for greater than in MongoDB queries [OK]

Hint: Use $gt, $lt for comparisons, not > or < directly [OK]

Common Mistakes:

• Using > directly in query object
• Mixing SQL syntax with MongoDB
• Assuming >= fixes the error

5. You have a blog application storing posts and comments. Why is a document database better than a relational one for storing posts with many comments?

hard

A. Because relational databases cannot store comments at all.

B. Because you can store each post and its comments together in one document, making reads faster.

C. Because document databases require all comments to be in separate collections.

D. Because relational databases do not support indexing on comments.

Solution

1. Step 1: Understand data embedding in document databases

   Document databases allow embedding related data (like comments) inside a single document (post).

2. Step 2: Compare with relational approach

   Relational databases store posts and comments in separate tables, requiring joins to combine them.

3. Step 3: Benefits of embedding

   Embedding comments inside posts reduces the need for joins and speeds up reading a post with its comments.

4. Final Answer:

   Because you can store each post and its comments together in one document, making reads faster. -> Option B

5. Quick Check:

   Embedding related data = faster reads [OK]

Hint: Embed related data in one document for faster access [OK]

Common Mistakes:

• Thinking relational DBs can't store comments
• Believing comments must be separate collections
• Assuming relational DBs lack indexing