Error-handling middleware in Express - Performance & Optimization

Performance: Error-handling middleware

MEDIUM IMPACT

This affects server response time and user experience by managing errors efficiently without blocking the event loop.

Handling errors in Express routes

Express

app.get('/data', (req, res, next) => {
  try {
    const data = getDataSync();
    if (!data) {
      throw new Error('Data not found');
    }
    res.send(data);
  } catch (err) {
    next(err);
  }
});

app.use((err, req, res, next) => {
  res.status(500).send({ error: err.message });
});

Using error-handling middleware catches errors synchronously and sends proper responses without crashing the server.

📈 Performance GainPrevents event loop blocking and improves server uptime and user experience.

Handling errors in Express routes

Express

app.get('/data', (req, res) => {
  const data = getDataSync();
  if (!data) {
    throw new Error('Data not found');
  }
  res.send(data);
});

Throwing errors directly inside route handlers without middleware causes unhandled exceptions and crashes the server.

📉 Performance CostBlocks event loop on error, causing server downtime and poor responsiveness.

Performance Comparison

Pattern	Event Loop Blocking	Error Handling	Server Stability	Verdict
Throw error directly in route	Blocks event loop on error	No centralized handling	Crashes server	[X] Bad
Use try-catch and next(err) in sync routes	Non-blocking	Centralized handling	Stable server	[OK] Good
Throw error in async route without next	Uncaught promise rejection	No handling	Potential memory leaks	[X] Bad
Use async try-catch with next(err)	Non-blocking	Centralized handling	Stable server	[OK] Good

Rendering Pipeline

Error-handling middleware intercepts errors during request processing and sends responses without blocking the event loop or crashing the server.

→Request Handling

→Response Sending

⚠️ BottleneckUnhandled errors causing event loop blocking or server crashes

Core Web Vital Affected

INP

This affects server response time and user experience by managing errors efficiently without blocking the event loop.

Optimization Tips

1Always use error-handling middleware with next(err) to avoid blocking the event loop.

2Wrap async route handlers in try-catch and call next(err) to catch promise rejections.

3Avoid throwing errors directly in routes without middleware to maintain server stability.

Performance Quiz - 3 Questions

What is the main performance risk of throwing errors directly inside Express route handlers without error middleware?

A It causes layout shifts in the browser

B It blocks the event loop and crashes the server

C It increases bundle size

D It slows down CSS rendering

DevTools: Network and Console panels

How to check: Open DevTools, go to Network to check server responses for error status codes; check Console for unhandled promise rejections or error logs.

What to look for: Look for 500 status responses handled gracefully and absence of unhandled promise rejection warnings.

Practice

1. What is the main purpose of error-handling middleware in Express?

easy

A. To serve static files like images and CSS

B. To parse incoming JSON request bodies

C. To catch errors and prevent the server from crashing

D. To log every request made to the server

Solution

1. Step 1: Understand middleware roles

   Middleware can serve many roles, but error-handling middleware specifically catches errors.

2. Step 2: Identify error-handling middleware purpose

   Error-handling middleware prevents the server from crashing by catching errors and responding properly.

3. Final Answer:

   To catch errors and prevent the server from crashing -> Option C

4. Quick Check:

   Error-handling middleware = catch errors [OK]

Hint: Error middleware catches errors to keep server running [OK]

Common Mistakes:

• Confusing error middleware with static file serving
• Thinking it parses request bodies
• Assuming it logs requests

2. Which of the following is the correct signature for an Express error-handling middleware function?

easy

A. (err, req, res, next)

B. (req, res, next)

C. (req, res)

D. (err, res, next)

Solution

1. Step 1: Recall error middleware parameters

   Error-handling middleware always has four parameters: err, req, res, next.

2. Step 2: Match the correct parameter order

   Only (err, req, res, next) has all four parameters in the correct order.

3. Final Answer:

   (err, req, res, next) -> Option A

4. Quick Check:

   Error middleware signature = (err, req, res, next) [OK]

Hint: Error middleware always has 4 parameters starting with err [OK]

Common Mistakes:

• Using only three parameters
• Omitting the err parameter
• Wrong parameter order

3. Given the code below, what will be the response if an error occurs in the route?

const express = require('express');
const app = express();

app.get('/', (req, res) => {
  throw new Error('Oops!');
});

app.use((err, req, res, next) => {
  res.status(500).send('Error caught: ' + err.message);
});

app.listen(3000);

medium

A. The client receives 'Error caught: Oops!' with status 500

B. The server crashes and stops running

C. The client receives a 404 Not Found error

D. The client receives an empty response with status 200

Solution

1. Step 1: Identify error thrown in route

   The route throws an error with message 'Oops!'.

2. Step 2: Check error-handling middleware response

   The error middleware catches the error and sends a 500 status with message including 'Oops!'.

3. Final Answer:

   The client receives 'Error caught: Oops!' with status 500 -> Option A

4. Quick Check:

   Error thrown = caught and sent with 500 [OK]

Hint: Thrown errors go to error middleware response [OK]

Common Mistakes:

• Expecting server crash on error
• Confusing 404 with error response
• Missing error message in response

4. What is wrong with the following error-handling middleware?

app.use((req, res, next, err) => {
  res.status(500).send('Error: ' + err.message);
});

medium

A. It should be placed before routes

B. The parameters are in the wrong order

C. It is missing the next() call

D. It should not have four parameters

Solution

1. Step 1: Check parameter order for error middleware

   Error middleware must have parameters in order: err, req, res, next.

2. Step 2: Identify incorrect order in code

   The code has (req, res, next, err) which is incorrect.

3. Final Answer:

   The parameters are in the wrong order -> Option B

4. Quick Check:

   Error middleware params order = err, req, res, next [OK]

Hint: Error middleware params start with err, not req [OK]

Common Mistakes:

• Swapping err and req parameters
• Placing error middleware before routes
• Forgetting to call next() when needed

5. You want to create an error-handling middleware that logs the error message and then passes the error to the next middleware. Which of the following implementations is correct?

A) app.use((err, req, res, next) => {
  console.log(err.message);
  next(err);
});

B) app.use((req, res, next, err) => {
  console.log(err.message);
  next();
});

C) app.use((err, req, res) => {
  console.log(err.message);
  next(err);
});

D) app.use((err, req, res, next) => {
  console.log(err.message);
  res.send('Error logged');
});

hard

A. app.use((err, req, res, next) => {
console.log(err.message);
res.send('Error logged');
});

B. app.use((req, res, next, err) => {
console.log(err.message);
next();
});

C. app.use((err, req, res) => {
console.log(err.message);
next(err);
});

D. app.use((err, req, res, next) => {
console.log(err.message);
next(err);
});

Solution

1. Step 1: Recall requirements for error-handling middleware that chains

   It must have four parameters starting with err, log err.message, and call next(err) to pass the error to the next handler.

2. Step 2: Match against provided implementations

   Implementations with incorrect parameter order or count fail to receive or handle err properly; those that respond instead of calling next(err) break the chain.

3. Final Answer:

   app.use((err, req, res, next) => {
     console.log(err.message);
     next(err);
   }); -> Option D

4. Quick Check:

   4 params + next(err) = correct chaining [OK]

Hint: Error middleware must have 4 params and call next(err) to continue [OK]

Common Mistakes:

• Wrong parameter order
• Forgetting next parameter
• Not calling next(err) to pass error along
• Sending response too early