Cache invalidation strategies in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is cache invalidation in the context of Express applications?

Cache invalidation is the process of removing or updating stored data in the cache when the original data changes, ensuring users get fresh and accurate information.

beginner

Name three common cache invalidation strategies used in Express apps.

1. Time-based expiration (TTL)
2. Manual invalidation (on data change)
3. Event-driven invalidation (triggered by events or hooks)

beginner

How does time-based expiration (TTL) work for cache invalidation?

It sets a time limit for cached data. After this time (TTL - Time To Live) expires, the cache is automatically cleared or refreshed.

intermediate

What is manual cache invalidation and when would you use it?

Manual invalidation means explicitly clearing or updating the cache when data changes, such as after a database update. Use it when data changes are known and you want precise control.

intermediate

Explain event-driven cache invalidation in Express.

Event-driven invalidation uses events or hooks in your app to clear or update cache automatically when certain actions happen, like saving new data or deleting records.

Which cache invalidation strategy automatically clears cache after a set time?

A Lazy loading

B Manual invalidation

C Event-driven invalidation

D Time-based expiration (TTL)

Time-based expiration uses a set time limit to clear cached data automatically.

When should manual cache invalidation be used in Express?

A When you want precise control after data updates

B When data changes are unpredictable

C When you want automatic cache clearing

D When cache never expires

Manual invalidation is best when you want to clear cache exactly after data changes.

What triggers event-driven cache invalidation?

A Specific app events or hooks

B A fixed timer

C User requests

D Random intervals

Event-driven invalidation happens when specific events or hooks in the app occur.

Which strategy might cause stale data if not carefully managed?

A Manual invalidation

B Time-based expiration with long TTL

C Event-driven invalidation

D No caching

Long TTL can keep stale data in cache longer before refreshing.

In Express, what is a common tool to implement caching and invalidation?

A Node.js File System

B MongoDB

C Redis

D Express Router

Redis is often used as a fast cache store with support for expiration and invalidation.

Describe the main cache invalidation strategies you can use in an Express app and when to use each.

Think about automatic vs manual ways to clear cache.

Explain why cache invalidation is important and what could happen if it is not done properly in a web app.

Consider user experience and data accuracy.

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