Middleware concept and execution flow in Node.js - Performance & Optimization

Performance: Middleware concept and execution flow

MEDIUM IMPACT

Middleware affects the server response time and throughput by adding processing steps before sending a response.

Adding multiple middleware functions to handle requests

Node.js

app.use(async (req, res, next) => { await heavyAsyncTask(); next(); });
app.use(async (req, res, next) => { await heavyAsyncTask(); next(); });

Using asynchronous tasks prevents blocking the event loop, allowing other requests to be processed.

📈 Performance GainNon-blocking, reduces response delay significantly under load

Adding multiple middleware functions to handle requests

Node.js

app.use((req, res, next) => { heavySyncTask(); next(); });
app.use((req, res, next) => { heavySyncTask(); next(); });

Synchronous heavy tasks block the event loop, delaying all requests.

📉 Performance CostBlocks event loop, increasing response time by 100+ ms per middleware

Performance Comparison

Pattern	Event Loop Blocking	Response Delay	Throughput Impact	Verdict
Synchronous heavy middleware	Blocks event loop	High delay	Reduces throughput	[X] Bad
Asynchronous middleware	Non-blocking	Low delay	Maintains throughput	[OK] Good
Static files served after auth	Non-blocking but delayed	Medium delay	Moderate throughput	[!] OK
Static files served first	Non-blocking	Low delay	High throughput	[OK] Good

Rendering Pipeline

Middleware runs on the server before the response is sent. It affects the server's processing time and how quickly the browser receives content.

→Server Processing

→Response Time

⚠️ BottleneckSynchronous or heavy middleware blocks the event loop, delaying response.

Optimization Tips

1Avoid synchronous blocking code in middleware to keep the event loop free.

2Order middleware to serve static files before heavy processing.

3Use asynchronous functions in middleware to improve server responsiveness.

Performance Quiz - 3 Questions

What is the main performance risk of synchronous middleware in Node.js?

A It blocks the event loop, delaying all requests

B It increases CSS rendering time

C It causes layout shifts in the browser

D It reduces JavaScript bundle size

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab to see response times. Use Performance tab to record server response delays and event loop blocking.

What to look for: Look for long server response times and blocked main thread indicating middleware delays.

Practice

1. What is the main purpose of middleware in a Node.js Express app?

easy

A. To style the HTML pages

B. To directly send responses to the client without routes

C. To define database schemas

D. To run code on requests before they reach the route handlers

Solution

1. Step 1: Understand middleware role and compare options

   Middleware functions run before route handlers to process requests. Only To run code on requests before they reach the route handlers describes middleware's role correctly; others describe unrelated tasks.

2. Final Answer:

   To run code on requests before they reach the route handlers -> Option D

3. Quick Check:

   Middleware = Pre-route code [OK]

Hint: Middleware runs before routes to handle requests [OK]

Common Mistakes:

• Thinking middleware sends responses directly
• Confusing middleware with database logic
• Assuming middleware styles pages

2. Which of the following is the correct way to define a middleware function in Express?

easy

A. app.get((req, res) => { console.log('Middleware'); });

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

C. app.middleware((req, res, next) => { next(); });

D. app.route('/').middleware((req, res) => { next(); });

Solution

1. Step 1: Recall Express middleware syntax and check options

   Middleware uses app.use() with (req, res, next) parameters. Only app.use((req, res, next) => { console.log('Middleware'); next(); }); uses app.use() and calls next(), which is correct middleware syntax.

2. Final Answer:

   app.use((req, res, next) => { console.log('Middleware'); next(); }); -> Option B

3. Quick Check:

   Middleware = app.use + next() [OK]

Hint: Middleware uses app.use and calls next() [OK]

Common Mistakes:

• Using app.get instead of app.use for middleware
• Missing next() call inside middleware
• Using non-existent app.middleware method

3. Consider this Express code:

app.use((req, res, next) => { console.log('First'); next(); });
app.use((req, res, next) => { console.log('Second'); next(); });
app.get('/', (req, res) => { res.send('Done'); });

What will be printed in the console when a GET request is made to '/'?

medium

A. First\nSecond

B. Second\nFirst

C. Done

D. No output

Solution

1. Step 1: Understand middleware execution order and route handler

   Middleware runs in the order added: first prints 'First', then calls next(), second prints 'Second'. After middleware, route handler sends response but does not print to console.

2. Final Answer:

   First\nSecond -> Option A

3. Quick Check:

   Middleware order = console logs order [OK]

Hint: Middleware logs appear in order added before route runs [OK]

Common Mistakes:

• Assuming route handler logs to console
• Thinking middleware runs in reverse order
• Missing next() causes no further logs

4. What is the problem with this middleware code?

app.use((req, res, next) => { console.log('Start'); });
app.get('/', (req, res) => { res.send('Hello'); });

medium

A. It calls next() twice, causing an error

B. It sends response twice, causing an error

C. It never calls next(), so the request hangs

D. It uses wrong parameters in middleware function

Solution

1. Step 1: Check middleware function and request flow effect

   The middleware logs 'Start' but does not call next(), so it blocks further processing. Without next(), the route handler never runs, so the request hangs.

2. Final Answer:

   It never calls next(), so the request hangs -> Option C

3. Quick Check:

   Missing next() blocks request [OK]

Hint: Always call next() in middleware unless sending response [OK]

Common Mistakes:

• Forgetting to call next() in middleware
• Calling next() multiple times
• Confusing middleware parameters

5. You want to add two middleware functions to log request time and check authentication before handling routes. Which code correctly ensures both run in order and the route handler executes after?

hard

A. app.use((req, res, next) => { console.log('Time:', Date.now()); next(); });\napp.use((req, res, next) => { if(req.user) next(); else res.status(401).send('Unauthorized'); });\napp.get('/', (req, res) => { res.send('Welcome'); });

B. app.use((req, res) => { console.log('Time:', Date.now()); });\napp.use((req, res, next) => { if(req.user) next(); else res.status(401).send('Unauthorized'); });\napp.get('/', (req, res) => { res.send('Welcome'); });

C. app.use((req, res, next) => { if(req.user) next(); else res.status(401).send('Unauthorized'); });\napp.use((req, res, next) => { console.log('Time:', Date.now()); next(); });\napp.get('/', (req, res) => { res.send('Welcome'); });

D. app.get('/', (req, res) => { console.log('Time:', Date.now()); });\napp.use((req, res, next) => { if(req.user) next(); else res.status(401).send('Unauthorized'); });

Solution

1. Step 1: Check middleware order, next() calls, and route handler execution

   app.use((req, res, next) => { console.log('Time:', Date.now()); next(); });\napp.use((req, res, next) => { if(req.user) next(); else res.status(401).send('Unauthorized'); });\napp.get('/', (req, res) => { res.send('Welcome'); }); runs time logger first, calls next(), then auth check middleware, which calls next() or sends response. Only if both middleware call next(), the route handler runs and sends 'Welcome'.

2. Final Answer:

   app.use((req, res, next) => { console.log('Time:', Date.now()); next(); });\napp.use((req, res, next) => { if(req.user) next(); else res.status(401).send('Unauthorized'); });\napp.get('/', (req, res) => { res.send('Welcome'); }); -> Option A

3. Quick Check:

   Middleware order + next() = correct flow [OK]

Hint: Middleware must call next() to continue chain in correct order [OK]

Common Mistakes:

• Missing next() in first middleware
• Reversing middleware order
• Using app.get instead of app.use for middleware