Finding and querying documents in Express - Performance & Optimization

Performance: Finding and querying documents

MEDIUM IMPACT

This affects server response time and how quickly the client receives data after a query.

Querying documents from a database in an Express app

Express

app.get('/users', async (req, res) => {
  const users = await User.find({ active: true }).limit(50);
  res.json(users);
});

Filters data and limits results to reduce server load and response size.

📈 Performance GainFaster query execution and smaller payload; improves LCP.

Querying documents from a database in an Express app

Express

app.get('/users', async (req, res) => {
  const users = await User.find();
  res.json(users);
});

Fetching all documents without filters can return large data sets, increasing response time and payload size.

📉 Performance CostBlocks response until all documents load; large payload increases network time.

Performance Comparison

Pattern	Server Processing	Network Payload	Response Time	Verdict
Query all documents without filters	High (full collection scan)	Large (all data sent)	Slow (blocks response)	[X] Bad
Query with filters and limit	Low (uses indexes)	Small (limited data)	Fast (quick response)	[OK] Good

Rendering Pipeline

Express queries run on the server before sending data to the browser. Slow queries delay the server response, which delays the browser's rendering start.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (database query execution)

Core Web Vital Affected

LCP

This affects server response time and how quickly the client receives data after a query.

Optimization Tips

1Always filter queries to return only needed documents.

2Use database indexes to speed up queries.

3Limit the number of documents returned to reduce payload size.

Performance Quiz - 3 Questions

What is a common performance issue when querying documents without filters in Express?

A Returning too many documents increases response time and payload size.

B Using filters slows down the query.

C Limiting results causes server errors.

D Queries without filters always use indexes.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR/fetch, and inspect the API request timing and payload size.

What to look for: Look for long waiting times or large response sizes indicating slow or heavy queries.

Practice

1. In Express with Mongoose, which method is used to find all documents matching a condition in a collection?

easy

A. Model.delete()

B. Model.create()

C. Model.update()

D. Model.find()

Solution

1. Step 1: Understand the purpose of Model.find()

   This method retrieves documents from the database that match the given query conditions.

2. Step 2: Differentiate from other methods

   Model.create() adds new documents, Model.update() modifies existing ones, and Model.delete() removes documents.

3. Final Answer:

   Model.find() -> Option D

4. Quick Check:

   Find documents = Model.find() [OK]

Hint: Use find() to get matching documents [OK]

Common Mistakes:

• Confusing find() with create()
• Using update() to retrieve documents
• Trying to delete documents to find them

2. Which of the following is the correct syntax to find all users with age 30 using Mongoose in Express?

easy

A. User.find({ age: 30 })

B. User.find(age == 30)

C. User.find('age: 30')

D. User.find({ 'age' = 30 })

Solution

1. Step 1: Use an object to specify query conditions

   The query must be an object with key-value pairs, like { age: 30 }.

2. Step 2: Check syntax correctness

   User.find({ age: 30 }) uses correct JavaScript object syntax. Options B, C, and D have syntax errors or wrong formats.

3. Final Answer:

   User.find({ age: 30 }) -> Option A

4. Quick Check:

   Query object syntax = User.find({ age: 30 }) [OK]

Hint: Use curly braces with key: value for queries [OK]

Common Mistakes:

• Using comparison operators inside find()
• Passing query as a string
• Using assignment (=) instead of colon (:) in object

3. What will be the output of this code snippet in Express using Mongoose?

const users = await User.find({ active: true }, 'name email');
console.log(users);

medium

A. An array of user objects with only 'name' and 'email' fields

B. An array of user objects with all fields including 'active'

C. A single user object with 'name' and 'email' fields

D. An error because projection syntax is wrong

Solution

1. Step 1: Understand the query parameters

   The first argument is the filter { active: true }, so only active users are returned.

2. Step 2: Understand the projection string

   The second argument 'name email' selects only these fields to be included in the returned documents.

3. Final Answer:

   An array of user objects with only 'name' and 'email' fields -> Option A

4. Quick Check:

   Projection limits fields = An array of user objects with only 'name' and 'email' fields [OK]

Hint: Second argument in find() selects fields to return [OK]

Common Mistakes:

• Expecting all fields to be returned
• Thinking projection returns a single object
• Using wrong projection syntax causing errors

4. Identify the error in this Mongoose query:

const results = await Product.find({ price: { $gt: 100 } }, { name, price });

medium

A. The find method cannot use async/await

B. The query operator $gt is invalid

C. The projection object is missing quotes around field names

D. The filter object should be a string

Solution

1. Step 1: Check the projection argument

   The projection should be an object with field names as strings or keys, like { name: 1, price: 1 }.

2. Step 2: Identify the syntax error

   Using { name, price } without values or quotes is invalid JavaScript object syntax here.

3. Final Answer:

   The projection object is missing quotes around field names -> Option C

4. Quick Check:

   Projection keys must be strings or key-value pairs [OK]

Hint: Projection keys need explicit values or quotes [OK]

Common Mistakes:

• Using shorthand object keys without values in projection
• Misunderstanding $gt operator
• Thinking async/await is invalid with find()

5. You want to find all orders where the status is 'shipped' and the total is greater than 50, but only return the order ID and total fields. Which is the correct Mongoose query in Express?

hard

A. Order.find({ status: 'shipped', total: { $gt: 50 } }, { _id: 1, total: 1 })

B. Order.find({ status: 'shipped', total: { $gt: 50 } }, '_id total')

C. Order.find({ status: 'shipped', total: { $gt: 50 } }, { _id: true, total: true })

D. Order.find({ status: 'shipped' && total > 50 }, '_id total')

Solution

1. Step 1: Write the correct filter object

   The filter must be { status: 'shipped', total: { $gt: 50 } } to find orders with status 'shipped' and total greater than 50.

2. Step 2: Use correct projection syntax

   Passing a string with space-separated field names like '_id total' is valid for projection in Mongoose.

3. Step 3: Evaluate options

   Order.find({ status: 'shipped', total: { $gt: 50 } }, { _id: 1, total: 1 }) uses an object projection with 1s which is valid but the question asks for the best correct query. Order.find({ status: 'shipped', total: { $gt: 50 } }, '_id total') uses string projection which is simpler and correct. Order.find({ status: 'shipped' && total > 50 }, '_id total') has invalid filter syntax. Order.find({ status: 'shipped', total: { $gt: 50 } }, { _id: true, total: true }) uses boolean true instead of 1 which is invalid in Mongoose projection.

4. Final Answer:

   Order.find({ status: 'shipped', total: { $gt: 50 } }, '_id total') -> Option B

5. Quick Check:

   Filter object + string projection = Order.find({ status: 'shipped', total: { $gt: 50 } }, '_id total') [OK]

Hint: Use object for filter, string for projection fields [OK]

Common Mistakes:

• Using logical operators incorrectly in filter
• Using boolean true instead of 1 in projection
• Passing projection as object with invalid values