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.