Request context middleware in Express - Performance & Optimization

Performance: Request context middleware

MEDIUM IMPACT

This affects server response time and throughput by adding processing steps per request.

Adding request-specific data accessible in all downstream handlers

Express

app.use((req, res, next) => {
  // Initialize empty context
  req.context = {};
  next();
});

app.get('/route', async (req, res) => {
  if (!req.context.data) {
    req.context.data = await fetchDataAsync();
  }
  res.send(req.context.data);
});

Defers expensive async operations to route handlers and avoids blocking middleware.

📈 Performance GainNon-blocking middleware improves throughput and reduces average response time by 30-100ms.

Adding request-specific data accessible in all downstream handlers

Express

app.use((req, res, next) => {
  // Heavy synchronous computation
  const data = expensiveSyncFunction();
  req.context = { data };
  next();
});

Blocking synchronous work delays every request, increasing server response time.

📉 Performance CostBlocks event loop for duration of expensiveSyncFunction, increasing response latency by 50-200ms depending on complexity.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous middleware	N/A	N/A	N/A	[X] Bad
Lightweight async middleware	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Request context middleware runs during the server's request handling pipeline before route handlers. It affects how fast the server can start processing and responding.

→Middleware Execution

→Request Handling

→Response Generation

⚠️ BottleneckSynchronous or heavy computations in middleware block the event loop, delaying all subsequent processing.

Optimization Tips

1Avoid heavy synchronous work in request context middleware to keep server responsive.

2Use asynchronous operations and lazy loading for data in middleware.

3Profile middleware execution time to identify bottlenecks.

Performance Quiz - 3 Questions

What is the main performance risk of heavy synchronous code in request context middleware?

A It blocks the event loop, delaying all requests.

B It increases client-side rendering time.

C It causes layout shifts in the browser.

D It reduces CSS selector efficiency.

DevTools: Performance

How to check: Record a server profile or use Node.js profiling tools to measure middleware execution time per request.

What to look for: Look for long blocking times in middleware functions that delay request handling.

Practice

1. What is the main purpose of request context middleware in Express?

easy

A. To serve static files like images and CSS

B. To handle database connections globally for all requests

C. To store and share data specific to each request across middleware and routes

D. To manage user authentication tokens only

Solution

1. Step 1: Understand request context middleware role

   Request context middleware stores data that belongs to a single request, making it accessible throughout that request's lifecycle.

2. Step 2: Compare with other options

   The other options describe different middleware roles but not the core purpose of request context middleware.

3. Final Answer:

   To store and share data specific to each request across middleware and routes -> Option C

4. Quick Check:

   Request context middleware = store per-request data [OK]

Hint: Remember: context middleware holds data per request only [OK]

Common Mistakes:

• Confusing request context with global app state
• Thinking it manages static files
• Assuming it only handles authentication

2. Which of the following is the correct way to add a property to the request context in Express middleware?

easy

A. req.context = { userId: 123 }; next();

B. res.context.userId = 123; next();

C. app.context.userId = 123; next();

D. context.userId = 123; next();

Solution

1. Step 1: Identify where to store request-specific data

   In Express, the request object (req) is unique per request, so adding a property to req is correct.

2. Step 2: Check other options for correctness

   res is for response, app is global, and context alone is undefined, so only req.context works properly.

3. Final Answer:

   req.context = { userId: 123 }; next(); -> Option A

4. Quick Check:

   Store data on req object for request context [OK]

Hint: Attach context data to req, not res or app [OK]

Common Mistakes:

• Using res or app instead of req for context
• Forgetting to call next() after middleware
• Assigning context to undefined variable

3. Given this middleware and route, what will be the output when a GET request is made to /user?

app.use((req, res, next) => {
  req.context = { user: 'Alice' };
  next();
});

app.get('/user', (req, res) => {
  res.send(`User: ${req.context.user}`);
});

medium

A. User: Alice

B. User: undefined

C. Error: Cannot read property 'user' of undefined

D. User:

Solution

1. Step 1: Analyze middleware setting req.context

   The middleware sets req.context to an object with user property 'Alice' before passing control.

2. Step 2: Check route handler usage

   The route reads req.context.user and sends it in the response, so it will output 'User: Alice'.

3. Final Answer:

   User: Alice -> Option A

4. Quick Check:

   Middleware sets req.context.user = 'Alice' [OK]

Hint: Middleware runs before route, so context is set [OK]

Common Mistakes:

• Assuming req.context is undefined in route
• Forgetting middleware runs before route
• Confusing res.context with req.context

4. Identify the error in this request context middleware code:

app.use((req, res, next) => {
  req.context.user = 'Bob';
  next();
});

medium

A. Middleware should not modify req object

B. req.context is undefined, so assigning user property causes an error

C. res object is used incorrectly

D. next() is missing, so request hangs

Solution

1. Step 1: Check initialization of req.context

   The code tries to assign user to req.context.user, but req.context was never created, so it's undefined.

2. Step 2: Understand the error cause

   Accessing a property on undefined causes a runtime error. next() is called, so no hanging issue.

3. Final Answer:

   req.context is undefined, so assigning user property causes an error -> Option B

4. Quick Check:

   Initialize req.context before adding properties [OK]

Hint: Always initialize req.context before use [OK]

Common Mistakes:

• Not initializing req.context as an object
• Forgetting to call next()
• Misusing res instead of req

5. You want to store a request ID in the context for every request and access it in multiple routes. Which is the best way to implement this in Express?

hard

A. Pass requestId as a query parameter in every route URL

B. Store requestId in a global variable and access it in routes

C. Attach requestId to res.locals and access it in routes

D. Create middleware that sets req.context = { requestId: uniqueId } and call next(), then read req.context.requestId in routes

Solution

1. Step 1: Understand request-specific data storage

   Request ID is unique per request, so it must be stored in a per-request object like req.context.

2. Step 2: Evaluate options for sharing data

   Global variables cause conflicts between concurrent requests, query parameters are not suitable for internal data sharing, and res.locals is primarily for template data rather than request processing.

3. Final Answer:

   Create middleware that sets req.context = { requestId: uniqueId } and call next(), then read req.context.requestId in routes -> Option D

4. Quick Check:

   Use req.context for per-request data sharing [OK]

Hint: Use middleware to set req.context with request ID [OK]

Common Mistakes:

• Using global variables for request data
• Relying on query parameters for context
• Confusing res.locals with request context