Middleware factory pattern in Express - Performance & Optimization

Performance: Middleware factory pattern

MEDIUM IMPACT

This pattern affects server response time and middleware execution efficiency in Express apps.

Creating middleware that needs configuration per route

Express

function loggerFactory(level) {
  return function logger(req, res, next) {
    console.log(`[${level}] ${req.method} ${req.url}`);
    next();
  };
}
app.use(loggerFactory('info'));

Configuration is done once when middleware is created, reducing per-request work.

📈 Performance Gainreduces CPU work per request, improving throughput

Creating middleware that needs configuration per route

Express

function logger(req, res, next) {
  const level = req.query.level || 'info';
  console.log(`[${level}] ${req.method} ${req.url}`);
  next();
}
app.use(logger);

Middleware recalculates config on every request causing unnecessary overhead.

📉 Performance Costadds CPU overhead on every request, increasing response time slightly

Performance Comparison

Pattern	Middleware Creation	Per-request Cost	CPU Overhead	Verdict
Direct middleware with config inside	Single instance	High (recomputes config)	High	[X] Bad
Middleware factory with config parameter	Multiple instances (once per config)	Low (uses preset config)	Low	[OK] Good

Rendering Pipeline

Middleware factory pattern affects the server-side request handling pipeline by optimizing middleware creation and execution.

→Middleware Initialization

→Request Handling

⚠️ BottleneckPer-request middleware execution with redundant computations

Optimization Tips

1Create middleware with configuration once using a factory function.

2Avoid recalculating settings inside middleware on every request.

3Reuse middleware instances to reduce CPU overhead and improve throughput.

Performance Quiz - 3 Questions

What is the main performance benefit of using a middleware factory pattern in Express?

A It reduces per-request computation by configuring middleware once.

B It increases the number of middleware functions executed per request.

C It delays middleware execution until after response is sent.

D It caches HTTP responses automatically.

DevTools: Node.js Profiler or Chrome DevTools Performance panel

How to check: Record CPU profile during requests, compare middleware execution time with and without factory pattern.

What to look for: Lower CPU time per request and fewer redundant computations indicate better performance.

Practice

1. What is the main purpose of the middleware factory pattern in Express?

easy

A. To automatically handle errors in middleware

B. To create middleware functions that can be customized with different settings

C. To replace the need for routing in Express

D. To speed up server response time by caching

Solution

1. Step 1: Understand middleware factory pattern concept

   The middleware factory pattern is used to create middleware functions that accept parameters to customize their behavior.

2. Step 2: Compare options with the concept

   Only To create middleware functions that can be customized with different settings correctly describes creating customizable middleware functions. Other options describe unrelated features.

3. Final Answer:

   To create middleware functions that can be customized with different settings -> Option B

4. Quick Check:

   Middleware factory pattern = customizable middleware [OK]

Hint: Middleware factory = function returning middleware with parameters [OK]

Common Mistakes:

• Thinking it automatically handles errors
• Confusing with routing or caching
• Believing it speeds response time directly

2. Which of the following is the correct syntax for a middleware factory function in Express?

easy

A. function logger() { /* middleware code */ }

B. function logger(req, res, next) { return function(level) { /* middleware code */ } }

C. function logger(level) { return function(req, res, next) { /* middleware code */ } }

D. function logger(level, req, res, next) { /* middleware code */ }

Solution

1. Step 1: Identify middleware factory structure

   A middleware factory is a function that takes parameters and returns a middleware function with signature (req, res, next).

2. Step 2: Match syntax to this pattern

   function logger(level) { return function(req, res, next) { /* middleware code */ } } matches this: it takes 'level' and returns a function with (req, res, next). Others do not follow this pattern.

3. Final Answer:

   function logger(level) { return function(req, res, next) { /* middleware code */ } } -> Option C

4. Quick Check:

   Factory returns middleware function = function logger(level) { return function(req, res, next) { /* middleware code */ } } [OK]

Hint: Factory takes params, returns (req, res, next) function [OK]

Common Mistakes:

• Placing req, res, next in factory parameters
• Not returning a middleware function
• Confusing middleware and factory signatures

3. Given the middleware factory below, what will be logged when a request is made?

function greet(name) {
  return function(req, res, next) {
    console.log(`Hello, ${name}!`);
    next();
  };
}

app.use(greet('Alice'));

medium

A. Hello, Alice!

B. Hello, undefined!

C. Hello, name!

D. No output, middleware does not log

Solution

1. Step 1: Understand middleware factory usage

   The factory greet('Alice') returns a middleware that logs 'Hello, Alice!'.

2. Step 2: Predict middleware behavior on request

   When a request comes, the middleware logs the greeting with the name 'Alice'.

3. Final Answer:

   Hello, Alice! -> Option A

4. Quick Check:

   Factory param used in log = Hello, Alice! [OK]

Hint: Factory param appears in log output [OK]

Common Mistakes:

• Expecting 'undefined' if factory param missing
• Thinking middleware does not log
• Confusing variable name with string literal

4. Identify the error in this middleware factory code:

function checkRole(role) {
  return function(req, res, next) {
    if(req.user.role === role) {
      next;
    } else {
      res.status(403).send('Forbidden');
    }
  };
}

medium

A. res.status should be res.send

B. Incorrect comparison operator in if statement

C. Middleware factory should not return a function

D. Missing parentheses when calling next()

Solution

1. Step 1: Review middleware function call

   Inside middleware, next must be called as a function: next().

2. Step 2: Identify the error

   The code uses 'next;' instead of 'next();', so middleware will not proceed correctly.

3. Final Answer:

   Missing parentheses when calling next() -> Option D

4. Quick Check:

   Call next() with parentheses [OK]

Hint: Always call next() as a function, not just next [OK]

Common Mistakes:

• Writing next without parentheses
• Confusing status and send methods
• Thinking factory should not return a function

5. You want to create a middleware factory that limits requests based on a max count per user. Which approach correctly applies the middleware factory pattern to achieve this?

hard

A. function rateLimiter(maxRequests) {
const counts = new Map();
return function(req, res, next) {
const user = req.user.id;
counts.set(user, (counts.get(user) || 0) + 1);
if(counts.get(user) > maxRequests) {
res.status(429).send('Too many requests');
} else {
next();
}
};
}

B. function rateLimiter(req, res, next, maxRequests) {
// logic here
}

C. function rateLimiter(maxRequests) {
return function(req, res) {
// missing next call
};
}

D. function rateLimiter() {
// no parameters, fixed limit
}

Solution

1. Step 1: Understand the requirement for customizable limit

   The middleware must accept maxRequests as a parameter to customize the limit.

2. Step 2: Check which option correctly returns middleware with (req, res, next) and uses maxRequests

   function rateLimiter(maxRequests) { const counts = new Map(); return function(req, res, next) { const user = req.user.id; counts.set(user, (counts.get(user) || 0) + 1); if(counts.get(user) > maxRequests) { res.status(429).send('Too many requests'); } else { next(); } }; } correctly implements a factory that returns middleware tracking counts and enforcing maxRequests, calling next() properly.

3. Final Answer:

   function rateLimiter(maxRequests) { const counts = new Map(); return function(req, res, next) { const user = req.user.id; counts.set(user, (counts.get(user) || 0) + 1); if(counts.get(user) > maxRequests) { res.status(429).send('Too many requests'); } else { next(); } }; } -> Option A

4. Quick Check:

   Factory with param returns middleware calling next() = function rateLimiter(maxRequests) { const counts = new Map(); return function(req, res, next) { const user = req.user.id; counts.set(user, (counts.get(user) || 0) + 1); if(counts.get(user) > maxRequests) { res.status(429).send('Too many requests'); } else { next(); } }; } [OK]

Hint: Factory takes limit param, returns middleware calling next() [OK]

Common Mistakes:

• Putting next as a factory parameter
• Not calling next() in middleware
• Not using maxRequests parameter