Cache framework configuration in Django - Mini Project: Build & Apply

Cache Framework Configuration in Django

📖 Scenario: You are building a Django web application that needs to speed up page loading by storing some data temporarily in cache. You will configure Django's cache framework step-by-step to use a simple in-memory cache backend.

🎯 Goal: Configure Django's cache framework by setting up the cache dictionary, adding a timeout value, applying the cache configuration in settings, and finally enabling caching for a view.

📋 What You'll Learn

Create a CACHES dictionary with a default backend

Add a TIMEOUT setting for cache expiration

Assign the CACHES dictionary to Django settings

Use the @cache_page decorator to cache a view

💡 Why This Matters

🌍 Real World

Caching helps websites load faster by storing data temporarily, reducing database hits and speeding up response times.

💼 Career

Understanding Django's cache framework is important for backend developers to optimize web application performance.

1

Create the cache dictionary

Create a dictionary called CACHES with a key 'default' that has a nested dictionary with 'BACKEND' set to 'django.core.cache.backends.locmem.LocMemCache'.

Django

# Your code here

Hint

Use a dictionary with key 'default' and set 'BACKEND' to the local memory cache backend string.

2

Add cache timeout setting

Add a TIMEOUT key inside the 'default' dictionary in CACHES and set it to 300 seconds.

Django

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
        # Add TIMEOUT here
    }
}

Hint

Add 'TIMEOUT': 300 inside the 'default' dictionary.

3

Assign cache configuration to settings

Assign the CACHES dictionary to a variable called settings.CACHES to apply the cache configuration in Django settings.

Django

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
        'TIMEOUT': 300
    }
}

# Assign CACHES to settings.CACHES
# Your code here

Hint

Import settings from django.conf and assign CACHES to settings.CACHES.

4

Enable caching on a view

Import cache_page from django.views.decorators.cache and decorate a view function called my_view with @cache_page(300) to cache its response for 300 seconds.

Django

from django.conf import settings

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
        'TIMEOUT': 300
    }
}

settings.CACHES = CACHES

from django.views.decorators.cache import cache_page

@cache_page(300)
def my_view(request):
    # Your view code here
    pass

Hint

Use @cache_page(300) above the my_view function definition.

Practice

1. What is the main purpose of configuring the CACHES setting in Django?

easy

A. To define the database connection details

B. To tell Django where and how to store temporary data for faster access

C. To set the URL routing rules

D. To configure user authentication methods

Solution

1. Step 1: Understand the role of caching

   Caching stores temporary data to speed up repeated requests by avoiding repeated work.

2. Step 2: Identify what CACHES configures

   The CACHES setting tells Django which backend to use and where to store cached data.

3. Final Answer:

   To tell Django where and how to store temporary data for faster access -> Option B

4. Quick Check:

   Cache config = store temp data [OK]

Hint: Cache config sets storage for temporary data [OK]

Common Mistakes:

• Confusing cache with database settings
• Thinking cache controls URL routing
• Mixing cache with authentication settings

2. Which of the following is the correct way to define a simple in-memory cache backend in Django's CACHES setting?

easy

A. 'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}

B. 'default': {'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache', 'LOCATION': '/var/tmp/django_cache'}

C. 'default': {'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '127.0.0.1:11211'}

D. 'default': {'BACKEND': 'django.core.cache.backends.db.DatabaseCache', 'LOCATION': 'my_cache_table'}

Solution

1. Step 1: Identify the in-memory cache backend

   The in-memory cache backend in Django is LocMemCache, which stores cache in local memory.

2. Step 2: Match the correct syntax

   'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'} correctly sets BACKEND to django.core.cache.backends.locmem.LocMemCache without needing a LOCATION.

3. Final Answer:

   'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'} -> Option A

4. Quick Check:

   In-memory cache = LocMemCache [OK]

Hint: LocMemCache is in-memory, no location needed [OK]

Common Mistakes:

• Adding LOCATION for LocMemCache unnecessarily
• Confusing file-based or DB cache for in-memory
• Using wrong backend string casing

3. Given this Django cache configuration snippet, what will be the cache backend used?

 CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.PyMemcacheCache',
        'LOCATION': '127.0.0.1:11211',
    }
}

medium

A. File-based cache storing data in /var/tmp

B. Local memory cache inside the Django process

C. Database cache storing data in a DB table

D. Memcached cache using PyMemcache client on localhost

Solution

1. Step 1: Read the BACKEND value

   The backend is set to django.core.cache.backends.memcached.PyMemcacheCache, which uses Memcached with the PyMemcache client.

2. Step 2: Check the LOCATION

   The location is 127.0.0.1:11211, the default Memcached server address on localhost.

3. Final Answer:

   Memcached cache using PyMemcache client on localhost -> Option D

4. Quick Check:

   Memcached backend = PyMemcache + localhost [OK]

Hint: Memcached backend with PyMemcache uses localhost:11211 [OK]

Common Mistakes:

• Confusing Memcached with file or DB cache
• Ignoring the LOCATION setting
• Assuming local memory cache instead

4. Identify the error in this Django cache configuration snippet:

 CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
        'LOCATION': '/tmp/django_cache'
    }
}

medium

A. LocMemCache backend should not have a LOCATION setting

B. The BACKEND string is misspelled

C. LOCATION path must be a database table name

D. The CACHES dictionary must be a list instead

Solution

1. Step 1: Understand LocMemCache usage

   LocMemCache stores cache in local memory and does not use a file path or location setting.

2. Step 2: Identify the incorrect LOCATION key

   Providing a LOCATION with a file path is invalid for LocMemCache and will cause an error.

3. Final Answer:

   LocMemCache backend should not have a LOCATION setting -> Option A

4. Quick Check:

   LocMemCache no LOCATION needed [OK]

Hint: LocMemCache ignores LOCATION, so don't set it [OK]

Common Mistakes:

• Adding LOCATION to LocMemCache
• Confusing file cache with memory cache
• Misunderstanding backend string format

5. You want to configure Django to use a database table named my_cache_table for caching. Which is the correct CACHES setting to achieve this?

hard

A. 'default': {'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': 'my_cache_table'}

B. 'default': {'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache', 'LOCATION': 'my_cache_table'}

C. 'default': {'BACKEND': 'django.core.cache.backends.db.DatabaseCache', 'LOCATION': 'my_cache_table'}

D. 'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache', 'LOCATION': 'my_cache_table'}

Solution

1. Step 1: Identify the backend for database caching

   The backend for caching in a database table is DatabaseCache.

2. Step 2: Set the LOCATION to the table name

   The LOCATION must be the name of the database table, here my_cache_table.

3. Final Answer:

   'default': {'BACKEND': 'django.core.cache.backends.db.DatabaseCache', 'LOCATION': 'my_cache_table'} -> Option C

4. Quick Check:

   DB cache backend + table name = correct config [OK]

Hint: DatabaseCache backend uses table name as LOCATION [OK]

Common Mistakes:

• Using file or memory cache backend for DB caching
• Setting LOCATION to a file path instead of table name
• Confusing Memcached with DB cache