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

Concept Flow - Cache invalidation strategies

Data changes in DB

↓

Identify cached data affected

↓

Choose invalidation strategy

↓

Delete cache

↓

Serve fresh data from cache

When data changes, Django identifies which cached data is affected, then either deletes or updates the cache to keep it fresh.

Execution Sample

Django

from django.core.cache import cache

# Invalidate cache key after data update
cache.delete('user_profile_42')

This code deletes a specific cache entry after user data changes to ensure fresh data is served next time.

Execution Table

Step	Action	Cache Key	Cache State Before	Cache State After	Result
1	Initial cache set	user_profile_42	None	{'user_profile_42': 'old_data'}	Cache stores old user data
2	User data updated in DB	-	{'user_profile_42': 'old_data'}	{'user_profile_42': 'old_data'}	Cache still has old data
3	Cache invalidation triggered	user_profile_42	{'user_profile_42': 'old_data'}	{}	Cache entry deleted
4	Next request fetches fresh data	user_profile_42	{}	{'user_profile_42': 'fresh_data'}	Cache updated with fresh data
5	Serve fresh data from cache	user_profile_42	{'user_profile_42': 'fresh_data'}	{'user_profile_42': 'fresh_data'}	User sees updated profile

💡 Cache invalidation ensures stale data is removed so fresh data is served after DB update

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
cache	{}	{'user_profile_42': 'old_data'}	{'user_profile_42': 'old_data'}	{}	{'user_profile_42': 'fresh_data'}	{'user_profile_42': 'fresh_data'}

Key Moments - 3 Insights

Why does the cache still have old data after the database update in step 2?

Because updating the database does not automatically update or delete the cache. The cache must be explicitly invalidated as shown in step 3.

What happens if we don't delete or update the cache after data changes?

The cache will serve stale data, causing users to see outdated information. Step 3 shows the importance of invalidation.

Can we update the cache directly instead of deleting it?

Yes, updating the cache with fresh data after DB changes is another strategy, as shown in step 4.

Visual Quiz - 3 Questions

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

A {}

B {'user_profile_42': 'old_data'}

C {'user_profile_42': 'fresh_data'}

D None

💡 Hint

Check the 'Cache State After' column for step 3 in the execution table.

At which step does the cache get updated with fresh data?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for when 'Cache State After' shows fresh data in the execution table.

If we skip cache deletion in step 3, what will the cache state be at step 4?

A {}

B {'user_profile_42': 'old_data'}

C {'user_profile_42': 'fresh_data'}

D None

💡 Hint

Refer to the cache state before and after deletion in the execution table.

Concept Snapshot

Cache Invalidation Strategies in Django:
- When data changes, identify affected cache keys.
- Invalidate cache by deleting keys or updating with fresh data.
- Use cache.delete('key') to remove stale entries.
- Always invalidate cache after DB updates to avoid stale data.
- Fresh data is cached on next request after invalidation.

Full Transcript

Cache invalidation in Django means removing or updating cached data when the original data changes. This prevents users from seeing old information. The process starts when data in the database changes. Django then finds which cached data is affected. It either deletes that cache entry or updates it with new data. For example, after updating a user's profile, the cache key 'user_profile_42' is deleted. The next time the profile is requested, fresh data is fetched from the database and stored in the cache. This way, the cache always serves up-to-date information. Without invalidation, the cache would keep serving old data, confusing users. So, always remember to invalidate cache after data changes.

Practice

1. What is the main purpose of cache invalidation in Django caching?

easy

A. To store data permanently without expiration

B. To keep cached data fresh and accurate

C. To increase the size of the cache

D. To disable caching completely

Solution

1. Step 1: Understand cache invalidation concept

   Cache invalidation means removing or updating cached data so it stays correct and up-to-date.

2. Step 2: Identify the purpose in Django caching

   In Django, cache invalidation ensures users see fresh data by removing outdated cache entries.

3. Final Answer:

   To keep cached data fresh and accurate -> Option B

4. Quick Check:

   Cache invalidation = fresh data [OK]

Hint: Cache invalidation means keeping data fresh [OK]

Common Mistakes:

• Thinking cache invalidation increases cache size
• Believing cache never expires
• Confusing cache invalidation with disabling cache

2. Which Django cache method is used to remove a specific cached item?

easy

A. cache.delete()

B. cache.clear()

C. cache.set()

D. cache.get()

Solution

1. Step 1: Recall Django cache methods

   cache.delete() removes a specific key from the cache, clearing that cached item.

2. Step 2: Differentiate from other methods

   cache.clear() removes all cache, cache.set() adds data, cache.get() retrieves data.

3. Final Answer:

   cache.delete() -> Option A

4. Quick Check:

   Remove specific cache = cache.delete() [OK]

Hint: Use cache.delete() to remove one cached item [OK]

Common Mistakes:

• Using cache.clear() to remove one item
• Confusing cache.set() with deletion
• Trying to delete cache with cache.get()

3. Given this code snippet, what will be the output if the cache key 'user_1' is deleted before retrieval?

from django.core.cache import cache
cache.set('user_1', 'Alice', timeout=300)
cache.delete('user_1')
result = cache.get('user_1', 'Not Found')
print(result)

medium

A. Not Found

B. Alice

C. None

D. Error

Solution

1. Step 1: Analyze cache.set and cache.delete calls

   The key 'user_1' is set to 'Alice' but then immediately deleted from cache.

2. Step 2: Check cache.get behavior after deletion

   Since 'user_1' was deleted, cache.get returns the default value 'Not Found'.

3. Final Answer:

   Not Found -> Option A

4. Quick Check:

   Deleted key returns default value [OK]

Hint: Deleted cache keys return default on get [OK]

Common Mistakes:

• Expecting 'Alice' after deletion
• Assuming cache.get returns None by default
• Thinking deletion causes error

4. Identify the error in this Django cache invalidation code:

from django.core.cache import cache
cache.set('page_data', 'content', timeout=600)
cache.delete('page_data')
cache.delete('page_data')

medium

A. cache.set() must be called after cache.delete()

B. cache.delete() requires a timeout argument

C. Deleting the same key twice causes an error

D. No error; deleting a non-existent key is safe

Solution

1. Step 1: Understand cache.delete behavior

   Deleting a key that does not exist does not cause an error in Django cache.

2. Step 2: Check the code sequence

   First delete removes 'page_data', second delete tries to remove it again safely without error.

3. Final Answer:

   No error; deleting a non-existent key is safe -> Option D

4. Quick Check:

   Deleting missing key is safe [OK]

Hint: Deleting missing cache keys is safe [OK]

Common Mistakes:

• Thinking deleting twice causes error
• Believing cache.delete needs timeout
• Assuming cache.set must follow delete

5. You want to ensure cached user profile data expires automatically after 10 minutes but also want to manually clear it when the user updates their profile. Which cache invalidation strategy combination is best?

hard

A. Use cache.clear() to remove all cache every 10 minutes

B. Only use cache.set() with timeout=600, no manual deletion

C. Use cache.set() with timeout=600 and call cache.delete() on profile update

D. Only use cache.delete() without timeout

Solution

1. Step 1: Understand automatic expiration

   Setting timeout=600 (10 minutes) makes cache auto-expire after that time.

2. Step 2: Understand manual invalidation need

   Calling cache.delete() on profile update removes stale cached data immediately.

3. Step 3: Combine both strategies

   Using both timeout and manual delete ensures fresh data and timely expiration.

4. Final Answer:

   Use cache.set() with timeout=600 and call cache.delete() on profile update -> Option C

5. Quick Check:

   Timeout + manual delete = best strategy [OK]

Hint: Combine timeout and manual delete for fresh cache [OK]

Common Mistakes:

• Relying only on timeout causes stale data after update
• Using cache.clear() removes all cache unnecessarily
• Deleting without timeout loses auto-expiration benefit