Why Middleware concept and execution flow in Node.js? - Purpose & Use Cases

The Big Idea

What if you could handle all common tasks for every request with just a few simple functions?

The Scenario

Imagine building a web server where you have to check user login, log requests, handle errors, and parse data manually for every single route.

The Problem

Doing all these checks and tasks manually in each route is repetitive, easy to forget, and makes your code messy and hard to maintain.

The Solution

Middleware lets you write small functions that run in order for every request, handling tasks like logging, authentication, and errors automatically and cleanly.

Before vs After

✗ Before

app.get('/data', (req, res) => { if (!req.user) { res.status(401).send('Login required'); return; } console.log('Request received'); /* handle data */ });

✓ After

app.use(loggingMiddleware); app.use(authMiddleware); app.get('/data', (req, res) => { /* handle data */ });

What It Enables

Middleware enables building clear, reusable, and organized request handling that scales easily as your app grows.

Real Life Example

In a shopping website, middleware can check if a user is logged in before allowing checkout, log every purchase request, and catch errors without repeating code in every route.

Key Takeaways

Manual checks in every route cause repeated and messy code.

Middleware runs functions in order for all requests automatically.

This makes your server code cleaner, reusable, and easier to maintain.

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