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?"