Why document databases over relational in MongoDB - Quick Recap

Recall & Review

beginner

What is a document database?

A document database stores data as documents, usually in JSON-like format, making it easy to store complex and nested data in one place.

beginner

How do document databases handle data structure compared to relational databases?

Document databases allow flexible, dynamic schemas where each document can have different fields, unlike relational databases that require fixed table schemas.

intermediate

Why might document databases be better for applications with evolving data models?

Because document databases do not require predefined schemas, they let developers change data structure easily without costly migrations.

intermediate

What is one performance advantage of document databases over relational databases?

Document databases can retrieve related data in a single read because related data is stored together in one document, reducing the need for complex joins.

intermediate

When might a relational database still be preferred over a document database?

When data requires strong consistency, complex transactions, and strict relationships, relational databases are often better suited.

What format do document databases typically use to store data?

A Key-value pairs only

B Tables with rows and columns

C JSON-like documents

D Flat files

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

Which is a key benefit of document databases over relational databases?

A No support for nested data

B Fixed schema for all data

C Requires complex joins for data retrieval

D Flexible schema allowing different fields per document

Document databases allow flexible schemas where each document can have different fields.

Why do document databases often perform faster for certain queries?

A They store related data together in one document

B They require multiple queries for related data

C They use complex joins

D They do not index data

Storing related data together reduces the need for joins and multiple queries, improving performance.

Which scenario favors using a relational database instead of a document database?

A Strong consistency and complex transactions

B Simple key-value lookups

C Storing large binary files

D Data with flexible and changing structure

Relational databases are better for strong consistency and complex transactions.

What is a common use case for document databases?

A Applications with fixed, unchanging data models

B Applications needing flexible, evolving data structures

C Systems requiring strict relational integrity

D Data warehousing with complex joins

Document databases excel when data models evolve and need flexibility.

Explain why document databases are often chosen over relational databases for modern web applications.

Think about how web apps change and need to store complex data.

Describe a situation where a relational database might be a better choice than a document database.

Consider financial or inventory systems.

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