Deleting documents in Express - Performance & Optimization

Performance: Deleting documents

MEDIUM IMPACT

This affects server response time and client perceived speed when removing data from a database via an Express API.

Deleting a document from a database in an Express route handler

Express

app.delete('/item/:id', async (req, res) => {
  try {
    const id = req.params.id;
    await db.collection('items').deleteOne({ _id: new ObjectId(id) });
    res.send('Deleted');
  } catch {
    res.status(500).send('Error');
  }
});

Using async/await allows non-blocking code and better error handling, improving server responsiveness.

📈 Performance GainNon-blocking event loop, faster response, better INP.

Deleting a document from a database in an Express route handler

Express

app.delete('/item/:id', (req, res) => {
  const id = req.params.id;
  db.collection('items').findOneAndDelete({ _id: new ObjectId(id) }, (err, result) => {
    if (err) return res.status(500).send('Error');
    res.send('Deleted');
  });
});

Using callback style with no async/await can cause callback hell and harder error handling, potentially blocking the event loop longer.

📉 Performance CostBlocks event loop during DB operation, increasing response time and INP.

Performance Comparison

Pattern	Server Blocking	Event Loop Impact	Response Time	Verdict
Callback with blocking DB call	High	Blocks event loop	Slower	[X] Bad
Async/await non-blocking DB call	Low	Non-blocking	Faster	[OK] Good

Rendering Pipeline

Deleting documents in Express affects server-side processing before the client receives updated content. It impacts the time until the client can interact with the updated UI.

→Server Processing

→Network Transfer

→Client Rendering

⚠️ BottleneckServer Processing during database deletion

Core Web Vital Affected

INP

This affects server response time and client perceived speed when removing data from a database via an Express API.

Optimization Tips

1Always use asynchronous non-blocking calls for database deletion.

2Avoid synchronous code that blocks the Node.js event loop.

3Handle errors properly to avoid server crashes and delays.

Performance Quiz - 3 Questions

What is the main performance benefit of using async/await for deleting documents in Express?

A It reduces the size of the response payload.

B It prevents blocking the event loop during database operations.

C It automatically caches deleted documents.

D It improves CSS rendering speed on the client.

DevTools: Network

How to check: Open DevTools, go to Network tab, perform the delete request, and observe the request duration.

What to look for: Look for long server response times indicating blocking operations during deletion.

Practice

1. What does the deleteOne() method do in Express when working with a database?

easy

A. Deletes a single document that matches the filter criteria.

B. Deletes all documents in the collection.

C. Updates a document instead of deleting it.

D. Finds a document but does not delete it.

Solution

1. Step 1: Understand deleteOne() purpose

   The deleteOne() method removes only one document that matches the given filter.

2. Step 2: Compare with other methods

   deleteMany() deletes multiple documents, and find() only retrieves data without deleting.

3. Final Answer:

   Deletes a single document that matches the filter criteria. -> Option A

4. Quick Check:

   deleteOne() = deletes one document [OK]

Hint: Remember: deleteOne removes just one matching document [OK]

Common Mistakes:

• Confusing deleteOne with deleteMany
• Thinking deleteOne updates documents
• Assuming deleteOne finds but does not delete

2. Which of the following is the correct syntax to delete a document by its ID using Mongoose in Express?

easy

A. Model.findByIdAndDelete(id, callback);

B. Model.deleteById(id);

C. Model.removeById(id);

D. Model.deleteOneById(id);

Solution

1. Step 1: Recall Mongoose method for deleting by ID

   The correct method is findByIdAndDelete() which deletes a document by its ID.

2. Step 2: Check syntax correctness

   Only Model.findByIdAndDelete(id, callback); matches the official Mongoose syntax.

3. Final Answer:

   Model.findByIdAndDelete(id, callback); -> Option A

4. Quick Check:

   Use findByIdAndDelete to delete by ID [OK]

Hint: Use findByIdAndDelete to remove by ID [OK]

Common Mistakes:

• Using non-existent methods like deleteById
• Confusing deleteOne with findByIdAndDelete
• Missing callback or async handling

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

Model.deleteMany({ status: 'inactive' })
  .then(result => console.log(result.deletedCount))
  .catch(err => console.error(err));

medium

A. An error because deleteMany does not return deletedCount.

B. The entire deleted documents array.

C. Number of documents deleted with status 'inactive'.

D. Undefined because deleteMany returns nothing.

Solution

1. Step 1: Understand deleteMany return value

   deleteMany() returns an object with deletedCount indicating how many documents were deleted.

2. Step 2: Analyze the console.log statement

   The code logs result.deletedCount, so it outputs the number of deleted documents matching the filter.

3. Final Answer:

   Number of documents deleted with status 'inactive'. -> Option C

4. Quick Check:

   deleteMany() returns deletedCount [OK]

Hint: deleteMany returns deletedCount in result object [OK]

Common Mistakes:

• Expecting deleted documents array
• Assuming deleteMany returns nothing
• Confusing deletedCount with total documents

4. Identify the error in this Express Mongoose code snippet for deleting a document:

Model.deleteOne({ _id: id }, (err, doc) => {
  if (err) console.log(err);
  else console.log(doc);
});

medium

A. The filter object is missing required fields.

B. The deleteOne method does not accept a callback.

C. The method should be deleteMany to delete one document.

D. The callback parameter doc should be result to access deletion info.

Solution

1. Step 1: Check callback parameters for deleteOne

   The second callback parameter is a result object, not the deleted document itself.

2. Step 2: Understand what doc represents

   It should be named result or similar to reflect it contains deletion info like deletedCount, not the document.

3. Final Answer:

   The callback parameter doc should be result to access deletion info. -> Option D

4. Quick Check:

   Callback gets result info, not deleted doc [OK]

Hint: Callback second param is result info, not deleted doc [OK]

Common Mistakes:

• Expecting deleted document in callback
• Using deleteMany when only one document needed
• Assuming deleteOne does not accept callbacks

5. You want to delete all documents where the field active is false, but only if the user confirms. Which Express code snippet correctly handles this with error checking?

hard

A. Model.deleteMany({ active: false }, (err, res) => {
if (err) throw err;
console.log(res);
});

B. if(confirm) {
Model.deleteMany({ active: false })
.then(res => console.log(`${res.deletedCount} deleted`))
.catch(err => console.error(err));
}

C. if(confirm) {
Model.deleteOne({ active: false })
.then(res => console.log(res))
.catch(err => console.error(err));
}

D. Model.deleteMany({ active: false })
.then(res => console.log(res.deletedCount))
.catch(err => console.error(err));

Solution

1. Step 1: Check user confirmation before deleting

   if(confirm) { Model.deleteMany({ active: false }) .then(res => console.log(`${res.deletedCount} deleted`)) .catch(err => console.error(err)); } uses an if(confirm) check to ensure deletion only happens after user confirmation.

2. Step 2: Verify deletion and error handling

   It uses deleteMany to delete all matching documents, logs the count, and catches errors properly.

3. Final Answer:

   if(confirm) { Model.deleteMany({ active: false }) .then(res => console.log(`${res.deletedCount} deleted`)) .catch(err => console.error(err)); } -> Option B

4. Quick Check:

   Confirm before delete, handle errors [OK]

Hint: Check confirm before deleteMany, handle errors in promise [OK]

Common Mistakes:

• Using deleteOne instead of deleteMany for multiple docs
• Not checking user confirmation before deleting
• Throwing errors instead of catching them