Cache invalidation strategies in Django

Introduction

Cache invalidation strategies help keep your cached data fresh and accurate. They decide when to update or remove stored data so users see the latest information.

When you want to update cached web pages after content changes.

When database records change and cached queries need refreshing.

When user-specific data in cache must reflect recent actions.

When you want to avoid showing outdated information to users.

When you want to improve performance but keep data reliable.

Syntax

Django

from django.core.cache import cache

# Example: Delete a cache key
cache.delete('my_key')

# Example: Set cache with timeout
cache.set('my_key', 'value', timeout=300)

# Example: Clear all cache
cache.clear()

Use cache.delete(key) to remove specific cached data.

Use timeout to set how long data stays cached before automatic invalidation.

Examples

Cache user profile data for 10 minutes (600 seconds).

Django

cache.set('user_42_profile', user_profile_data, timeout=600)

Remove cached user profile when it changes.

Django

cache.delete('user_42_profile')

Clear all cached data, useful after big updates.

Django

cache.clear()

Sample Program

This example caches a product list, then updates it by deleting the old cache and setting a new one. Finally, it prints the updated cached list.

Django

from django.core.cache import cache

# Simulate caching a product list
products = ['apple', 'banana', 'cherry']
cache.set('product_list', products, timeout=120)

# Later, product list changes
products.append('date')

# Invalidate old cache
cache.delete('product_list')

# Update cache with new list
cache.set('product_list', products, timeout=120)

# Retrieve and print cached product list
cached_products = cache.get('product_list')
print(cached_products)

Important Notes

Always delete or update cache when underlying data changes to avoid stale info.

Use timeouts to automatically expire cache if manual invalidation is missed.

Be careful with cache.clear() as it removes all cached data, which might affect performance.

Summary

Cache invalidation keeps cached data fresh and accurate.

Use cache.delete() to remove specific cached items.

Set timeouts to auto-expire cached data after some time.

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