What Is Middleware in Express? A Simple Analogy Explained

If you enjoy this story, feel free to give it a like or share with your friends!

---

I’m in charge of a giant relay race. Each runner in the race has a specific role, just like components in a software application. But here’s the twist: before passing the baton to the next runner, each participant can make a decision or perform an action based on the current situation. This is my world of middleware in Express.

In this race, each runner represents a middleware function. When the baton, which symbolizes a request, is handed over, the runner can choose to perform a task. Some runners check the weather to ensure the race conditions are safe, akin to middleware checking for valid data or user authentication. If it’s too stormy, they might decide to pause the race, much like stopping the request from proceeding if there’s an error.

Other runners might apply sunscreen to prevent sunburn, just as middleware might modify request data or add headers for security. Some runners might even have water stations, keeping the team hydrated, similar to how middleware can log information or manage sessions.

As the baton moves from one runner to the next, each one contributes to the smooth progress of the race. Eventually, the baton reaches the finish line, where the final runner delivers it to the endpoint, completing the journey. This is like sending a response back to the client after passing through all necessary middleware.

---

JavaScript Code Example

Here’s a simple code snippet illustrating middleware in Express:

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

// Middleware function to log request details
function logRequestDetails(req, res, next) {
    console.log(`${req.method} request for '${req.url}'`);
    next(); // Pass control to the next middleware function
}

// Middleware function for authentication
function authenticateUser(req, res, next) {
    const userAuthenticated = true; // Simplified authentication check
    if (userAuthenticated) {
        next(); // User is authenticated, proceed to the next middleware
    } else {
        res.status(401).send('Authentication required');
    }
}

// Apply middleware to our app
app.use(logRequestDetails);
app.use(authenticateUser);

// Define a route
app.get('/', (req, res) => {
    res.send('Welcome to the home page!');
});

// Start the server
app.listen(3000, () => {
    console.log('Server is running on port 3000');
});

Explanation

1. Log Request Details: This middleware logs the HTTP method and URL of each incoming request. It’s like a runner checking the current weather conditions and ensuring everything is in order before passing the baton.
2. Authenticate User: This middleware checks if the user is authenticated. If the user is validated, it calls next() to move to the next runner (or middleware). If not, it sends a response and stops the baton from going further.
3. Middleware Application: By using app.use(), we apply these middleware functions to our Express app. They’ll run sequentially for each incoming request, just like runners in our race passing the baton.

Key Takeaways

• Middleware Functions: In Express, middleware functions are like runners in a relay race, each performing a specific task before passing control.
• Flow Control: The next() function is crucial as it dictates whether the baton (request) should move to the next runner (middleware).
• Flexible and Modular: Middleware allows for separation of concerns, as each function handles a specific aspect of request processing.