Cache invalidation strategies in Express - Step-by-Step Execution

Concept Flow - Cache invalidation strategies

Request comes in

↓

Check cache for data

↓

Serve response

↓

Trigger cache invalidation?

↓

End process

This flow shows how a request checks cache first, serves cached data if found, otherwise fetches fresh data and caches it. Cache invalidation happens after data changes to keep cache fresh.

Execution Sample

Express

app.get('/data', async (req, res) => {
  const cached = cache.get('data');
  if (cached) return res.send(cached);
  const fresh = await fetchData();
  cache.set('data', fresh);
  res.send(fresh);
});

This code checks cache for 'data'. If found, it returns cached data. Otherwise, it fetches fresh data, caches it, then returns it.

Execution Table

Step	Action	Cache State	Response Sent	Cache Invalidation
1	Request received for /data	{}	No	No
2	Check cache for 'data'	{}	No	No
3	Cache miss, fetch fresh data	{}	No	No
4	Store fresh data in cache	{'data': freshData}	No	No
5	Send fresh data in response	{'data': freshData}	Yes	No
6	Data updated elsewhere, invalidate cache	{}	No	Yes
7	Next request checks cache again	{}	No	No
8	Cache miss again, fetch fresh data	{}	No	No
9	Store fresh data in cache	{'data': freshData2}	No	No
10	Send fresh data in response	{'data': freshData2}	Yes	No

💡 Process ends after response sent and cache updated or invalidated as needed.

Variable Tracker

Variable	Start	After Step 4	After Step 6	After Step 9	Final
cache	{}	{'data': freshData}	{}	{'data': freshData2}	{'data': freshData2}
responseSent	No	No	No	No	Yes

Key Moments - 3 Insights

Why do we check the cache before fetching fresh data?

Checking the cache first (see step 2) avoids unnecessary data fetching, making responses faster and reducing load.

When and why do we invalidate the cache?

Cache is invalidated after data changes (step 6) to prevent serving outdated information, ensuring users get fresh data.

What happens if we don't invalidate the cache after data updates?

Without invalidation, the cache keeps old data, so users may see stale responses, causing inconsistency.

Visual Quiz - 3 Questions

Look at the execution table, what is the cache state after step 4?

A {'data': freshData2}

B {}

C {'data': freshData}

D null

💡 Hint

Check the 'Cache State' column at step 4 in the execution_table.

At which step does cache invalidation occur?

A Step 6

B Step 5

C Step 3

D Step 9

💡 Hint

Look at the 'Cache Invalidation' column for the step marked 'Yes'.

If cache invalidation did not happen at step 6, what would be the cache state at step 7?

A {}

B {'data': freshData}

C {'data': freshData2}

D null

💡 Hint

Refer to variable_tracker for cache state changes and consider what happens if invalidation is skipped.

Concept Snapshot

Cache Invalidation Strategies in Express:
- Check cache before fetching data.
- Serve cached data if available.
- Fetch and cache fresh data if cache miss.
- Invalidate cache after data changes to avoid stale data.
- Common invalidation: remove or update cache entries.
- Keeps responses fast and data fresh.

Full Transcript

Cache invalidation strategies in Express involve checking if requested data is already stored in cache. If yes, the cached data is sent immediately, speeding up response. If not, fresh data is fetched from the source, stored in cache, then sent. When data changes elsewhere, the cache must be invalidated by removing or updating the cached entry. This prevents serving outdated information. The process repeats for each request, ensuring fast and fresh responses.

Practice

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

easy

A. To permanently store data without expiration

B. To increase server CPU usage

C. To keep cached data fresh and up-to-date

D. To disable caching completely

Solution

1. Step 1: Understand cache invalidation

   Cache invalidation means removing or updating cached data when it becomes outdated.

2. Step 2: Purpose in Express apps

   Express uses cache invalidation to ensure users get fresh data, not stale cached content.

3. Final Answer:

   To keep cached data fresh and up-to-date -> Option C

4. Quick Check:

   Cache invalidation = fresh data [OK]

Hint: Cache invalidation means keeping data fresh [OK]

Common Mistakes:

• Thinking cache invalidation disables caching
• Confusing cache invalidation with permanent storage
• Believing it increases CPU usage intentionally

2. Which of the following is the correct way to set a Cache-Control header in Express to prevent caching?

easy

A. res.set('Cache-Control', 'max-age=3600')

B. res.set('Cache-Control', 'no-store')

C. res.set('Cache-Control', 'public, max-age=86400')

D. res.set('Cache-Control', 'private, max-age=600')

Solution

1. Step 1: Understand Cache-Control values

   'no-store' tells browsers not to cache the response at all.

2. Step 2: Identify the option that prevents caching

   res.set('Cache-Control', 'no-store') uses 'no-store', which disables caching completely.

3. Final Answer:

   res.set('Cache-Control', 'no-store') -> Option B

4. Quick Check:

   Prevent caching = 'no-store' [OK]

Hint: Use 'no-store' to disable caching in Cache-Control [OK]

Common Mistakes:

• Using 'max-age' which allows caching
• Confusing 'private' with disabling cache
• Missing quotes around header value

3. Consider this Express middleware code snippet:

app.use((req, res, next) => {
  res.set('Cache-Control', 'public, max-age=10');
  next();
});

app.get('/data', (req, res) => {
  res.json({ time: Date.now() });
});

What will happen if a user requests /data twice within 10 seconds?

medium

A. The second request will return cached data from the first request

B. The second request will always fetch fresh data from the server

C. The server will throw an error on the second request

D. The cache will be cleared after the first request

Solution

1. Step 1: Analyze Cache-Control header

   'public, max-age=10' means cache is valid for 10 seconds.

2. Step 2: Effect on repeated requests

   Within 10 seconds, the browser or proxy can serve cached response without contacting server.

3. Final Answer:

   The second request will return cached data from the first request -> Option A

4. Quick Check:

   max-age=10 caches for 10 seconds [OK]

Hint: max-age sets cache duration in seconds [OK]

Common Mistakes:

• Assuming server always sends fresh data
• Confusing 'public' with disabling cache
• Thinking cache clears immediately after first request

4. You wrote this Express route to disable caching:

app.get('/info', (req, res) => {
  res.set('Cache-Control', 'no-cache');
  res.json({ message: 'Hello' });
});

But clients still see cached responses. What is the likely problem?

medium

A. Express does not support Cache-Control headers

B. The header name "Cache-Control" is misspelled

C. res.json() automatically overrides Cache-Control headers

D. Using "no-cache" allows caching but requires revalidation

Solution

1. Step 1: Understand "no-cache" meaning

   'no-cache' means caches can store response but must revalidate before reuse.

2. Step 2: Why clients see cached data

   If revalidation is skipped or proxy ignores it, cached data may be served.

3. Final Answer:

   Using "no-cache" allows caching but requires revalidation -> Option D

4. Quick Check:

   'no-cache' means revalidate before reuse [OK]

Hint: "no-cache" means revalidate, not disable caching [OK]

Common Mistakes:

• Thinking 'no-cache' disables caching completely
• Assuming header name is wrong without checking
• Believing res.json() removes headers

5. You want to cache user profile data in Express but ensure it updates immediately after a user changes their info. Which cache invalidation strategy is best?

hard

A. Set a long max-age and manually clear cache on user update

B. Use 'no-store' to never cache user profiles

C. Set a short max-age and rely on automatic expiration

D. Cache indefinitely and ignore updates

Solution

1. Step 1: Understand caching user profiles

   User profiles benefit from caching for speed but must update after changes.

2. Step 2: Choose invalidation strategy

   Long max-age improves performance; manual cache clearing on update ensures fresh data.

3. Final Answer:

   Set a long max-age and manually clear cache on user update -> Option A

4. Quick Check:

   Manual invalidation + long cache = fresh and fast [OK]

Hint: Use manual cache clear after updates for fresh user data [OK]

Common Mistakes:

• Using 'no-store' loses caching benefits
• Relying only on short max-age causes frequent reloads
• Ignoring cache invalidation leads to stale data