Cache middleware pattern in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of cache middleware in Express?

Cache middleware stores responses temporarily to speed up repeated requests, reducing server load and response time.

beginner

How does cache middleware improve user experience?

By serving stored responses quickly, it makes pages load faster, similar to how a bookmark helps you quickly find a favorite page.

intermediate

In Express, where is cache middleware placed in the request flow?

Cache middleware is placed before the route handler to check if a cached response exists and send it immediately if found.

intermediate

What is a simple way to implement cache middleware in Express?

Use an in-memory object to store responses keyed by request URL, then check this cache in middleware before processing the request.

intermediate

Why should cache middleware handle cache expiration?

To avoid serving outdated data, cache middleware should remove or refresh cached responses after a set time, like clearing old notes.

What does cache middleware do in an Express app?

A Logs every request to the console

B Stores and serves repeated responses quickly

C Authenticates users before access

D Parses JSON request bodies

Cache middleware stores responses to serve them faster on repeated requests.

Where should cache middleware be placed in Express middleware chain?

A After error handling middleware

B After the route handler

C Before the route handler

D At the end of all middleware

Cache middleware must run before route handlers to check for cached responses.

What is a common key used to store cached responses?

A Request URL

B User password

C Response status code

D Request headers

Request URL uniquely identifies the resource to cache the response.

Why is cache expiration important in cache middleware?

A To encrypt cached data

B To speed up the server startup

C To log cache hits

D To prevent serving outdated data

Expiration ensures users get fresh data by removing old cached responses.

Which of these is NOT a benefit of cache middleware?

A Automatic user authentication

B Faster response times

C Reduced server load

D Lower bandwidth usage

Cache middleware does not handle authentication.

Explain how cache middleware works in an Express app and why it is useful.

Think about how a shortcut helps you avoid repeating work.

Describe how you would implement a simple cache middleware in Express.

Imagine saving your favorite recipes in a notebook for quick access.

Practice

1. What is the main purpose of cache middleware in an Express app?

easy

A. To handle user authentication

B. To store responses and speed up repeated requests

C. To parse incoming JSON data

D. To log all incoming requests

Solution

1. Step 1: Understand cache middleware role

   Cache middleware stores responses temporarily to avoid repeating expensive operations.

2. Step 2: Compare with other middleware roles

   Authentication, parsing, and logging serve different purposes unrelated to caching.

3. Final Answer:

   To store responses and speed up repeated requests -> Option B

4. Quick Check:

   Cache middleware = store responses [OK]

Hint: Cache middleware speeds up repeated requests by storing responses [OK]

Common Mistakes:

• Confusing cache with authentication middleware
• Thinking cache parses request bodies
• Assuming cache logs requests

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

easy

A. function cache(req, res, next) { next(); res.send(cacheData); }

B. function cache(req, res) { res.send(cacheData); next(); }

C. function cache(req, res, next) { if (cacheData) res.send(cacheData); else next(); }

D. function cache(req, next, res) { if (cacheData) res.send(cacheData); else next(); }

Solution

1. Step 1: Check middleware signature

   Express middleware functions take (req, res, next) in that order.

2. Step 2: Verify control flow

   If cached data exists, send it; otherwise, call next() to continue processing.

3. Final Answer:

   function cache(req, res, next) { if (cacheData) res.send(cacheData); else next(); } -> Option C

4. Quick Check:

   Middleware signature and flow = function cache(req, res, next) { if (cacheData) res.send(cacheData); else next(); } [OK]

Hint: Middleware must have (req, res, next) and call next() if no cache [OK]

Common Mistakes:

• Wrong parameter order in middleware function
• Calling next() after sending response
• Not calling next() when cache miss

3. Given this cache middleware snippet, what will be the output if cacheData is { message: 'Hello' }?

function cache(req, res, next) {
  if (cacheData) {
    res.json(cacheData);
  } else {
    next();
  }
}

app.get('/greet', cache, (req, res) => {
  res.json({ message: 'Hi there!' });
});

medium

A. {"message":"Hello"}

B. {"message":"Hi there!"}

C. Error: cacheData is undefined

D. No response sent

Solution

1. Step 1: Check cacheData value

   cacheData is defined as { message: 'Hello' }, so the if condition is true.

2. Step 2: Determine middleware behavior

   Since cacheData exists, middleware sends JSON response and does not call next().

3. Final Answer:

   {"message":"Hello"} -> Option A

4. Quick Check:

   cacheData present sends cached response [OK]

Hint: If cacheData exists, middleware sends it and skips next() [OK]

Common Mistakes:

• Assuming next() runs even if cacheData exists
• Confusing JSON string with object
• Expecting original handler response

4. Identify the bug in this cache middleware code:

let cacheData;

function cache(req, res, next) {
  if (cacheData) {
    res.send(cacheData);
  }
  next();
}

medium

A. Middleware function missing req parameter

B. cacheData is not initialized

C. res.send should be res.json

D. next() is called even after sending a response

Solution

1. Step 1: Analyze control flow

   If cacheData exists, res.send(cacheData) sends a response, but next() is still called afterward.

2. Step 2: Understand Express behavior

   Calling next() after sending a response can cause errors or duplicate responses.

3. Final Answer:

   next() is called even after sending a response -> Option D

4. Quick Check:

   Calling next() after res.send causes errors [OK]

Hint: Do not call next() after sending a response [OK]

Common Mistakes:

• Calling next() unconditionally after res.send
• Ignoring middleware flow control
• Assuming res.send and next() can run together

5. You want to implement cache middleware that stores responses for 10 seconds and then expires. Which approach correctly achieves this in Express?

hard

A. Store response in cacheData with a timestamp; clear cacheData if older than 10 seconds before sending

B. Use setTimeout to clear cacheData every 10 seconds regardless of requests

C. Send cached response only if cacheData exists, without checking time

D. Clear cacheData manually by restarting the server every 10 seconds

Solution

1. Step 1: Understand cache expiration logic

   Cache should store data with a timestamp and check age before sending cached response.

2. Step 2: Evaluate options

   Store response in cacheData with a timestamp; clear cacheData if older than 10 seconds before sending checks timestamp and clears stale cache before responding, ensuring fresh data.

3. Final Answer:

   Store response in cacheData with a timestamp; clear cacheData if older than 10 seconds before sending -> Option A

4. Quick Check:

   Cache expiration needs timestamp check [OK]

Hint: Use timestamps to expire cache, not just timers or manual clears [OK]

Common Mistakes:

• Ignoring cache expiration timing
• Clearing cache blindly without request context
• Relying on server restart to clear cache