Collections vs tables mental model in MongoDB - Performance Comparison

Time Complexity: Collections vs tables mental model

O(n)

Understanding Time Complexity

When working with databases, it's helpful to understand how collections in MongoDB compare to tables in traditional databases.

We want to see how operations on collections grow as data size increases, similar to tables.

Scenario Under Consideration

Analyze the time complexity of querying all documents from a MongoDB collection.

    db.users.find({})
      .toArray()
      .then(users => {
        // process users
      })
    

This code fetches all documents from the 'users' collection and converts them to an array.

Identify Repeating Operations

Look for repeated actions that affect performance.

• Primary operation: Reading each document in the collection.
• How many times: Once for every document in the collection.

How Execution Grows With Input

As the number of documents grows, the time to read all documents grows too.

Input Size (n)	Approx. Operations
10	10 document reads
100	100 document reads
1000	1000 document reads

Pattern observation: The work grows directly with the number of documents.

Final Time Complexity

Time Complexity: O(n)

This means the time to read all documents grows linearly with the number of documents.

Common Mistake

[X] Wrong: "Fetching all documents is always fast regardless of collection size."

[OK] Correct: As the collection grows, reading every document takes more time, so it slows down.

Interview Connect

Understanding how collections behave like tables helps you explain database performance clearly and confidently.

Self-Check

"What if we add an index to the collection? How would the time complexity of searching change?"

Practice

1. Which of the following best describes a MongoDB collection compared to a SQL table?

easy

A. A collection requires a strict schema like SQL tables.

B. A collection stores data in fixed rows and columns.

C. A collection stores flexible documents without fixed columns.

D. A collection cannot store multiple records.

Solution

1. Step 1: Understand SQL tables

   SQL tables store data in rows and columns with a fixed schema, meaning each row has the same columns.

2. Step 2: Understand MongoDB collections

   MongoDB collections store documents that can have different fields and structures, so they are flexible and schema-less.

3. Final Answer:

   A collection stores flexible documents without fixed columns. -> Option C

4. Quick Check:

   Collections = flexible documents [OK]

Hint: Collections are flexible; tables have fixed columns [OK]

Common Mistakes:

• Thinking collections have fixed columns like tables
• Assuming collections require strict schemas
• Believing collections cannot hold multiple documents

2. Which of the following is the correct way to create a collection named users in MongoDB?

easy

A. db.createCollection('users');

B. db.users.create();

C. CREATE TABLE users;

D. CREATE COLLECTION users;

Solution

1. Step 1: Recall MongoDB syntax for creating collections

   MongoDB uses the method db.createCollection('name') to create a collection explicitly.

2. Step 2: Check other options

   CREATE COLLECTION users; and C use SQL syntax, which is invalid in MongoDB. db.users.create(); is not a valid MongoDB command.

3. Final Answer:

   db.createCollection('users'); -> Option A

4. Quick Check:

   MongoDB collection creation = db.createCollection() [OK]

Hint: Use db.createCollection('name') to create collections [OK]

Common Mistakes:

• Using SQL syntax like CREATE TABLE
• Trying to call create() on collection name
• Omitting quotes around collection name

3. Given a MongoDB collection products with documents:

{"name": "Pen", "price": 1.5}

{"name": "Notebook", "price": 3.0, "color": "blue"}

What will db.products.find({}) return?

medium

A. All documents including fields like name, price, and color if present.

B. Only documents with the price field.

C. Only documents with the color field.

D. An error because documents have different fields.

Solution

1. Step 1: Understand find({}) query

   The query find({}) returns all documents in the collection regardless of their fields.

2. Step 2: Check document fields

   Documents can have different fields in MongoDB collections; this does not cause errors or filtering.

3. Final Answer:

   All documents including fields like name, price, and color if present. -> Option A

4. Quick Check:

   find({}) returns all documents [OK]

Hint: find({}) returns all documents regardless of fields [OK]

Common Mistakes:

• Thinking find({}) filters by fields
• Expecting errors due to different document structures
• Assuming only documents with certain fields are returned

4. You tried to insert documents with different fields into a MongoDB collection but got an error. What is the most likely cause?

medium

A. MongoDB collections require all documents to have the same fields.

B. MongoDB does not allow inserting multiple documents.

C. You forgot to create the collection before inserting.

D. You used SQL INSERT syntax instead of MongoDB insert methods.

Solution

1. Step 1: Recall MongoDB insert syntax

   MongoDB uses insertOne() or insertMany() methods, not SQL INSERT statements.

2. Step 2: Understand document flexibility

   MongoDB collections allow documents with different fields; this does not cause errors.

3. Final Answer:

   You used SQL INSERT syntax instead of MongoDB insert methods. -> Option D

4. Quick Check:

   MongoDB insert = insertOne()/insertMany() [OK]

Hint: Use MongoDB insertOne()/insertMany(), not SQL INSERT [OK]

Common Mistakes:

• Assuming MongoDB requires fixed schema
• Not creating collection first (MongoDB auto-creates collections)
• Believing MongoDB forbids multiple inserts

5. You want to migrate a SQL table with fixed columns to MongoDB. Which approach best fits MongoDB's collection model?

hard

A. Keep the exact SQL schema and enforce it strictly in MongoDB.

B. Store each row as a document with the same fields, but allow optional fields for future flexibility.

C. Convert the table into multiple collections, each with one column as documents.

D. Store all rows as a single large document with arrays for each column.

Solution

1. Step 1: Understand MongoDB document flexibility

   MongoDB collections store documents that can have different fields, so keeping the same fields but allowing optional ones fits well.

2. Step 2: Evaluate other options

   Convert the table into multiple collections, each with one column as documents. breaks data into many collections unnecessarily. Keep the exact SQL schema and enforce it strictly in MongoDB. tries to enforce strict schema, which MongoDB does not require. Store all rows as a single large document with arrays for each column. stores all data in one document, which is inefficient and not recommended.

3. Final Answer:

   Store each row as a document with the same fields, but allow optional fields for future flexibility. -> Option B

4. Quick Check:

   MongoDB collections = flexible documents per row [OK]

Hint: Migrate rows as flexible documents with optional fields [OK]

Common Mistakes:

• Trying to enforce strict SQL schema in MongoDB
• Splitting columns into separate collections
• Storing all rows in one big document