Index direction (ascending vs descending) in MongoDB - When to Use Which

The Big Idea

Discover how a simple choice in sorting direction can speed up your data searches dramatically!

The Scenario

Imagine you have a huge phone book sorted by last names. You want to find all people whose last names start with 'M'. Without any order, you'd have to flip through every page one by one.

The Problem

Searching manually through an unordered list is slow and tiring. You might miss entries or waste time flipping back and forth. It's easy to get lost or make mistakes when the data isn't organized clearly.

The Solution

Using index direction, like ascending or descending order, organizes data so you can quickly jump to the right spot. It's like having the phone book sorted from A to Z or Z to A, making searches fast and reliable.

Before vs After

✗ Before

db.contacts.find({lastName: {$gte: 'M', $lt: 'N'}})

✓ After

db.contacts.createIndex({lastName: 1})  // ascending index

What It Enables

It lets databases find and sort data lightning-fast, improving user experience and saving time.

Real Life Example

When you scroll through a social media feed sorted by newest posts first (descending), the index direction helps load those posts instantly without delay.

Key Takeaways

Manual searching through unordered data is slow and error-prone.

Index direction organizes data ascending or descending for quick access.

This makes searching and sorting efficient and reliable.

Practice

1. What does the index direction 1 mean in MongoDB indexes?

easy

A. Descending order

B. No order

C. Ascending order

D. Random order

Solution

1. Step 1: Understand index direction values

   In MongoDB, index direction 1 means ascending order, and -1 means descending order.

2. Step 2: Match the value to the meaning

   Since the question asks about 1, it corresponds to ascending order.

3. Final Answer:

   Ascending order -> Option C

4. Quick Check:

   Index direction 1 = Ascending order [OK]

Hint: 1 means ascending, -1 means descending [OK]

Common Mistakes:

• Confusing 1 with descending order
• Thinking 1 means no order
• Mixing up ascending and descending

2. Which of the following is the correct syntax to create a descending index on the field age in MongoDB?

easy

A. db.collection.createIndex({ age: 1 })

B. db.collection.createIndex({ age: -1 })

C. db.collection.createIndex({ age: 'desc' })

D. db.collection.createIndex({ age: 'descending' })

Solution

1. Step 1: Recall MongoDB index syntax for direction

   MongoDB uses 1 for ascending and -1 for descending in index creation.

2. Step 2: Identify the correct descending syntax

   The correct way to create a descending index on age is { age: -1 }.

3. Final Answer:

   db.collection.createIndex({ age: -1 }) -> Option B

4. Quick Check:

   Descending index uses -1 [OK]

Hint: Use -1 for descending index direction [OK]

Common Mistakes:

• Using string values like 'desc' instead of -1
• Using 1 which means ascending
• Incorrect object syntax

3. Given the index { name: 1, score: -1 }, which query will use this index efficiently?

medium

A. db.collection.find().sort({ name: 1, score: -1 })

B. db.collection.find().sort({ name: -1, score: 1 })

C. db.collection.find().sort({ score: -1, name: 1 })

D. db.collection.find().sort({ name: 1 })

Solution

1. Step 1: Understand compound index direction

   The index sorts name ascending and score descending.

2. Step 2: Match query sort order with index

   Only the query sorting { name: 1, score: -1 } matches the index directions exactly, so it uses the index efficiently.

3. Final Answer:

   db.collection.find().sort({ name: 1, score: -1 }) -> Option A

4. Quick Check:

   Sort matches index directions exactly [OK]

Hint: Sort order must match index directions exactly [OK]

Common Mistakes:

• Reversing sort directions
• Changing field order in sort
• Using partial sort that doesn't match index

4. You created an index with { date: 1, price: -1 } but your query sorts by { price: -1, date: 1 }. What is the problem?

medium

A. The index fields order does not match the sort order

B. The index direction values are invalid

C. MongoDB does not support mixed ascending and descending indexes

D. The query syntax is incorrect

Solution

1. Step 1: Check index field order

   The index is created with fields date then price.

2. Step 2: Compare query sort order

   The query sorts by price first, then date, which does not match the index field order.

3. Final Answer:

   The index fields order does not match the sort order -> Option A

4. Quick Check:

   Field order in sort must match index order [OK]

Hint: Index and sort field order must match exactly [OK]

Common Mistakes:

• Assuming direction values are invalid
• Thinking MongoDB disallows mixed directions
• Blaming query syntax instead of order

5. You want to optimize queries that sort by category ascending and then by rating descending. Which index should you create?

hard

A. db.collection.createIndex({ rating: -1, category: 1 })

B. db.collection.createIndex({ category: -1, rating: 1 })

C. db.collection.createIndex({ rating: 1, category: -1 })

D. db.collection.createIndex({ category: 1, rating: -1 })

Solution

1. Step 1: Identify query sort order

   The queries sort by category ascending and rating descending.

2. Step 2: Create matching compound index

   The index must have category with direction 1 and rating with direction -1 in that order.

3. Final Answer:

   db.collection.createIndex({ category: 1, rating: -1 }) -> Option D

4. Quick Check:

   Index matches query sort directions and order [OK]

Hint: Match index fields and directions to query sort exactly [OK]

Common Mistakes:

• Reversing field order in index
• Swapping ascending and descending directions
• Creating index on wrong fields