When not to index in MongoDB - Step-by-Step Execution

Concept Flow - When not to index

Start: Need to decide on indexing?

↓

Check: Is the field frequently queried?

No→Do NOT index

Yes↓

Check: Is the collection small?

Yes→Indexing may be unnecessary

No↓

Check: Is the field updated very often?

Yes→Avoid indexing to reduce overhead

No↓

Create index

↓

End

Decide whether to index by checking query frequency, collection size, and update frequency to avoid unnecessary overhead.

Execution Sample

MongoDB

db.users.find({age: 30})
// Query on 'age' field
// Decide if 'age' should be indexed
// Conditions: frequent query? collection size? update frequency?

This example shows deciding whether to index the 'age' field in the users collection based on usage patterns.

Execution Table

Step	Condition Checked	Condition Result	Action Taken	Reason
1	Is 'age' frequently queried?	Yes	Proceed to next check	Field is used often in queries
2	Is collection small (<1000 docs)?	No	Proceed to next check	Collection is large enough to benefit from index
3	Is 'age' field updated frequently?	Yes	Do NOT index	Indexing overhead on frequent updates is high
4	Exit	N/A	No index created	Avoid performance cost on writes

💡 Stopped indexing because 'age' field is updated frequently, causing high overhead

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
frequent_query	unknown	Yes	Yes	Yes	Yes
collection_small	unknown	unknown	No	No	No
field_updated_often	unknown	unknown	unknown	Yes	Yes
index_decision	undecided	undecided	undecided	No	No

Key Moments - 2 Insights

Why should we avoid indexing fields that are updated very often?

Because each update requires updating the index too, which slows down write operations as shown in step 3 of the execution_table.

If the collection is very small, why might indexing be unnecessary?

Because scanning a small collection is fast enough, so the overhead of maintaining an index may not be worth it, as seen in step 2.

Visual Quiz - 3 Questions

Look at the execution_table, what is the reason for not creating an index?

A The field is not frequently queried

B The field is updated frequently

C The collection is too small

D The query is too complex

💡 Hint

Check step 3 in the execution_table where the decision to not index is made due to frequent updates

At which step does the decision to avoid indexing happen?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Action Taken' column in the execution_table to find when indexing is stopped

If the 'age' field was not updated frequently, what would be the next step after confirming frequent queries and large collection?

A Do NOT index

B Check if collection is small

C Create index

D Stop querying

💡 Hint

Refer to the flow in concept_flow and the execution_table steps 1 and 2

Concept Snapshot

When not to index:
- Avoid indexing fields updated very often to reduce write overhead.
- Small collections may not need indexes as scans are fast.
- Index fields frequently used in queries.
- Indexing adds overhead on writes.
- Decide based on query frequency, collection size, and update frequency.

Full Transcript

This lesson shows when you should not create an index in MongoDB. First, check if the field is often used in queries. If not, no index is needed. If yes, check if the collection is small; small collections may not benefit from indexes. Then check if the field is updated frequently. If it is, avoid indexing because indexes slow down updates. The example shows a field 'age' that is queried often but updated frequently, so indexing is avoided to keep writes fast.