Router level middleware in Express - Performance & Optimization

Performance: Router-level middleware

MEDIUM IMPACT

This affects server response time and throughput by controlling how requests are processed and routed.

Applying middleware to all routes vs specific routes

Express

router.use('/specific-path', (req, res, next) => { /* logic */ next(); });

Middleware runs only on matching routes, reducing overhead.

📈 Performance Gainreduces CPU usage and speeds up unrelated route handling

Applying middleware to all routes vs specific routes

Express

app.use((req, res, next) => { /* heavy logic */ next(); });

Middleware runs on every request, even when not needed, causing extra processing.

📉 Performance Costadds unnecessary CPU work on every request, increasing response time

Performance Comparison

Pattern	CPU Usage	Blocking	Request Latency	Verdict
Global middleware on all routes	High	No	Increased	[X] Bad
Middleware scoped to specific routes	Low	No	Reduced	[OK] Good
Synchronous blocking middleware	High	Yes	Severely Increased	[X] Bad
Asynchronous non-blocking middleware	Moderate	No	Optimized	[OK] Good

Rendering Pipeline

Router-level middleware affects the server-side request processing pipeline before response is sent to the client.

→Request Parsing

→Routing

→Middleware Execution

→Response Generation

⚠️ BottleneckMiddleware Execution when inefficient or blocking

Optimization Tips

1Apply middleware only to routes that need it to avoid extra processing.

2Use asynchronous code in middleware to prevent blocking the server.

3Avoid heavy computations in middleware to keep response times low.

Performance Quiz - 3 Questions

What is a performance risk of applying router-level middleware globally to all routes?

A Middleware reduces server CPU usage.

B Middleware runs on every request, adding unnecessary processing.

C Middleware only runs on matching routes, improving speed.

D Middleware automatically caches responses.

DevTools: Performance (Node.js profiling tools or Chrome DevTools for Node)

How to check: Record a CPU profile while sending requests; look for long middleware execution times or blocking calls.

What to look for: High CPU usage or long blocking tasks in middleware functions indicate performance issues.

Practice

1. What is the main purpose of router-level middleware in Express?

easy

A. To replace the main app middleware completely

B. To run middleware only for routes defined in a specific router

C. To handle errors globally across all routers

D. To serve static files from a directory

Solution

1. Step 1: Understand router-level middleware scope

   Router-level middleware runs only for routes defined in that router, not the entire app.

2. Step 2: Compare with other middleware types

   Main app middleware runs for all routes, error middleware handles errors, static middleware serves files. Router middleware is specific to router routes.

3. Final Answer:

   To run middleware only for routes defined in a specific router -> Option B

4. Quick Check:

   Router middleware scope = specific router routes [OK]

Hint: Router middleware affects only its router's routes [OK]

Common Mistakes:

• Confusing router middleware with app-level middleware
• Thinking router middleware handles errors globally
• Assuming router middleware serves static files

2. Which of the following is the correct way to add middleware to an Express router?

easy

A. router.middleware(function(req, res, next) { next(); });

B. router.add(function(req, res, next) { next(); });

C. app.useRouter(function(req, res, next) { next(); });

D. router.use(function(req, res, next) { next(); });

Solution

1. Step 1: Recall Express router middleware syntax

   The correct method to add middleware to a router is router.use().

2. Step 2: Check other options for validity

   router.middleware, app.useRouter, and router.add are not valid Express methods.

3. Final Answer:

   router.use(function(req, res, next) { next(); }); -> Option D

4. Quick Check:

   Use router.use() to add middleware [OK]

Hint: Use router.use() to add middleware to routers [OK]

Common Mistakes:

• Using non-existent methods like router.middleware or router.add
• Confusing app.useRouter with router.use
• Forgetting to call next() inside middleware

3. Consider this Express router code:

const express = require('express');
const router = express.Router();

router.use((req, res, next) => {
  console.log('Middleware A');
  next();
});

router.get('/test', (req, res) => {
  res.send('Hello from test');
});

module.exports = router;

What will be printed in the console when a client requests /test on this router?

medium

A. Middleware A

B. Hello from test

C. Middleware A and then Hello from test

D. Nothing will be printed

Solution

1. Step 1: Identify middleware behavior on route request

   The router middleware logs 'Middleware A' and calls next(), so it runs before the route handler.

2. Step 2: Understand console output vs response

   The console.log prints 'Middleware A' to the server console. The response sends 'Hello from test' to the client but does not print to console.

3. Final Answer:

   Middleware A -> Option A

4. Quick Check:

   Middleware console.log prints 'Middleware A' [OK]

Hint: Middleware logs to console, route sends response [OK]

Common Mistakes:

• Confusing console output with response content
• Expecting both console and response text in console
• Ignoring the next() call in middleware

4. Given this router code:

const router = require('express').Router();

router.use((req, res, next) => {
  console.log('First middleware');
  next();
});

router.get('/hello', (req, res) => {
  res.send('Hello World');
});

router.use((req, res) => {
});

What is the problem with this code?

medium

A. The last middleware does not call next(), causing requests to hang

B. The last middleware is missing next() and will cause 404 for all routes

C. The last middleware will never run because it is after a route handler

D. The last middleware should have 4 parameters to handle errors

Solution

1. Step 1: Analyze middleware execution order

   Middleware and routes execute in the order defined. First middleware runs for all requests and calls next().

2. Step 2: Trace unmatched route behavior

   For unmatched routes like /foo: first middleware calls next(), /hello route doesn't match so next(), last middleware runs but does nothing--no response and no next() call.

3. Step 3: Identify the consequence

   The request pipeline stops without a response, causing the client request to hang indefinitely.

4. Final Answer:

   The last middleware does not call next(), causing requests to hang -> Option A

5. Quick Check:

   No response + no next() = request hangs [OK]

Hint: Every middleware must either respond or call next() [OK]

Common Mistakes:

• Thinking empty catch-all middleware is harmless
• Forgetting unmatched routes reach the last middleware
• Assuming the router automatically handles 404s

5. You want to apply a logging middleware only to routes under /api in your Express app. You create a router and add middleware like this:

const express = require('express');
const app = express();
const apiRouter = express.Router();

apiRouter.use((req, res, next) => {
  console.log('API request:', req.method, req.url);
  next();
});

apiRouter.get('/users', (req, res) => {
  res.send('User list');
});

app.use('/api', apiRouter);

app.get('/', (req, res) => {
  res.send('Home');
});

What will happen when a client requests /api/users and /?

hard

A. Logging middleware does not run for any route

B. Logging middleware runs for both /api/users and /

C. Logging middleware runs only for /api/users, not for /

D. Logging middleware runs only for / route

Solution

1. Step 1: Understand router mounting path

   The router is mounted at '/api', so its middleware runs only for routes starting with '/api'.

2. Step 2: Analyze requests

   Request to '/api/users' triggers the router middleware and route handler. Request to '/' goes directly to app.get('/') and skips router middleware.

3. Final Answer:

   Logging middleware runs only for /api/users, not for / -> Option C

4. Quick Check:

   Router middleware runs only on mounted path routes [OK]

Hint: Router middleware runs only on its mounted path routes [OK]

Common Mistakes:

• Assuming router middleware runs for all app routes
• Confusing app-level and router-level middleware scopes
• Expecting middleware to run for '/' when mounted on '/api'