Middleware vs decorator pattern in Node.js - Performance Comparison

Performance: Middleware vs decorator pattern

MEDIUM IMPACT

This concept affects how requests are processed and how code execution impacts response time and resource usage in Node.js applications.

Adding reusable logic to HTTP request handling

Node.js

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

Using asynchronous non-blocking tasks in middleware keeps event loop free, improving responsiveness.

📈 Performance GainReduces blocking, lowers INP, improves throughput

Adding reusable logic to HTTP request handling

Node.js

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

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

📉 Performance CostBlocks event loop, increasing INP and response latency

Performance Comparison

Pattern	Event Loop Blocking	CPU Usage	Throughput Impact	Verdict
Synchronous middleware with heavy tasks	High	High	Low throughput due to blocking	[X] Bad
Asynchronous middleware with light tasks	Low	Low	High throughput, responsive	[OK] Good
Synchronous decorator wrapping heavy function	High	High	Blocks event loop during calls	[X] Bad
Async decorator wrapping lightweight async function	Low	Low	Non-blocking, smooth execution	[OK] Good

Rendering Pipeline

In Node.js, middleware and decorators affect the event loop and CPU usage rather than browser rendering. Middleware chains process requests sequentially, potentially blocking the event loop if synchronous. Decorators wrap functions adding overhead per call. Both impact responsiveness and throughput.

→Event Loop

→CPU Processing

⚠️ BottleneckBlocking synchronous code in middleware or decorators

Core Web Vital Affected

INP

This concept affects how requests are processed and how code execution impacts response time and resource usage in Node.js applications.

Optimization Tips

1Avoid synchronous heavy tasks in middleware to prevent event loop blocking.

2Use asynchronous code in decorators to keep function calls non-blocking.

3Minimize the number of middleware layers to reduce overhead per request.

Performance Quiz - 3 Questions

Which pattern causes more event loop blocking in Node.js?

A Synchronous middleware with heavy tasks

B Asynchronous middleware with light tasks

C Async decorator wrapping lightweight async function

D No middleware or decorators

DevTools: Performance (Node.js Profiler)

How to check: Run Node.js with --inspect flag, open Chrome DevTools, record CPU profile during requests, and analyze event loop blocking and CPU usage.

What to look for: Look for long blocking tasks in middleware or decorators causing event loop delays and high CPU usage spikes.

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