Middleware vs decorator pattern in Node.js - When to Use Which

The Big Idea

Discover how to keep your code neat while adding powerful features effortlessly!

The Scenario

Imagine building a web server where you have to add logging, authentication, and error handling by writing the same code inside every function that handles requests.

The Problem

Manually adding these features everywhere is tiring, easy to forget, and makes your code messy and hard to change later.

The Solution

Middleware and decorator patterns let you add these extra features in one place, so your main code stays clean and you can reuse the added behavior easily.

Before vs After

✗ Before

function handleRequest(req, res) {
  console.log('Request received');
  if (!req.user) { res.status(401).send('Unauthorized'); return; }
  try {
    // main logic
  } catch (e) {
    res.status(500).send('Error');
  }
}

✓ After

app.use(loggingMiddleware);
app.use(authMiddleware);
app.use(errorHandlingMiddleware);
app.get('/data', mainHandler);

What It Enables

You can build flexible, clean, and reusable code that adds features like logging or security without touching your main logic.

Real Life Example

Think of a coffee shop where the barista focuses on making coffee, while other staff handle taking orders, payments, and cleaning separately--each with their own role but working together smoothly.

Key Takeaways

Manual repetition of extra features is slow and error-prone.

Middleware and decorators add behavior cleanly and reuse it.

This keeps your code simple and easier to maintain.

Practice

1. What is the main difference between middleware and decorator patterns in Node.js?

easy

A. Middleware wraps functions; decorators process requests in a chain.

B. Middleware is only for error handling; decorators only for logging.

C. Middleware and decorators are the same and used interchangeably.

D. Middleware processes requests in a chain; decorators wrap functions to add behavior.

Solution

1. Step 1: Understand middleware role

   Middleware functions run one after another to handle requests or responses in a chain.

2. Step 2: Understand decorator role

   Decorators wrap a function to add or modify its behavior without changing the original function.

3. Final Answer:

   Middleware processes requests in a chain; decorators wrap functions to add behavior. -> Option D

4. Quick Check:

   Middleware = chain, Decorator = wrap [OK]

Hint: Middleware chains; decorators wrap functions [OK]

Common Mistakes:

• Confusing middleware with decorators
• Thinking middleware wraps functions
• Assuming both are identical

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

easy

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

B. function middleware(req, res) { return next(); }

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

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

Solution

1. Step 1: Recall Express middleware signature

   Middleware functions take three parameters in order: request, response, and next function.

2. Step 2: Check parameter order and usage

   function middleware(req, res, next) { next(); } correctly uses (req, res, next) and calls next() to pass control.

3. Final Answer:

   function middleware(req, res, next) { next(); } -> Option A

4. Quick Check:

   Middleware signature = (req, res, next) [OK]

Hint: Middleware params order: req, res, next [OK]

Common Mistakes:

• Mixing parameter order
• Forgetting to call next()
• Returning next() instead of calling

3. Consider this decorator function in Node.js:

function logDecorator(fn) {
  return function(...args) {
    console.log('Calling function');
    return fn(...args);
  };
}

function greet(name) {
  return `Hello, ${name}!`;
}

const decoratedGreet = logDecorator(greet);
console.log(decoratedGreet('Alice'));

What will be printed to the console?

medium

A. Calling function\nHello, Alice!

B. Hello, Alice!\nCalling function

C. Calling function

D. Hello, Alice!

Solution

1. Step 1: Understand decorator behavior

   The decorator wraps greet, logging 'Calling function' before calling greet.

2. Step 2: Trace function calls and output

   Calling decoratedGreet('Alice') logs 'Calling function' then returns 'Hello, Alice!'. Both are printed by console.log.

3. Final Answer:

   Calling function\nHello, Alice! -> Option A

4. Quick Check:

   Decorator logs then calls function [OK]

Hint: Decorator logs before calling wrapped function [OK]

Common Mistakes:

• Assuming only greeting prints
• Confusing order of console logs
• Missing decorator wrapping effect

4. This Express middleware is intended to log request URLs but has a bug:

function logger(req, res, next) {
  console.log('Request URL:', req.url);
  next;
}

What is the bug and how to fix it?

medium

A. Middleware must return a value; fix by adding return next()

B. req.url is undefined; fix by using req.path

C. next is not called as a function; fix by changing to next()

D. console.log syntax is wrong; fix by adding parentheses

Solution

1. Step 1: Identify middleware flow control

   Middleware must call next() as a function to continue the chain.

2. Step 2: Spot the bug in next usage

   Code uses next without parentheses, so next middleware is never called.

3. Final Answer:

   next is not called as a function; fix by changing to next() -> Option C

4. Quick Check:

   Call next() to continue middleware chain [OK]

Hint: Always call next() as a function in middleware [OK]

Common Mistakes:

• Writing next instead of next()
• Assuming req.url is invalid
• Thinking middleware must return a value

5. You want to add authentication to an existing function without changing it. Which pattern fits best and why?

function fetchData(userId) {
  return `Data for user ${userId}`;
}

hard

A. Modify fetchData directly to add authentication logic inside.

B. Use a decorator to wrap fetchData and check authentication before calling it.

C. Use middleware to process fetchData since it handles requests in a chain.

D. Use middleware to wrap fetchData because middleware wraps functions.

Solution

1. Step 1: Understand the goal

   You want to add authentication without changing fetchData itself.

2. Step 2: Choose the right pattern

   Decorators wrap functions to add behavior like authentication without modifying original code.

3. Final Answer:

   Use a decorator to wrap fetchData and check authentication before calling it. -> Option B

4. Quick Check:

   Decorator = add behavior without changing function [OK]

Hint: Decorator wraps function to add features without changes [OK]

Common Mistakes:

• Confusing middleware with decorators
• Modifying original function directly
• Thinking middleware wraps functions