14

Rendering and Caching Content

In the previous chapter, you used model inheritance and generic relations to create flexible course content models. You implemented a custom model field, and you built a course management system using class-based views. Finally, you created a JavaScript drag-and-drop functionality using asynchronous HTTP requests to order course modules and their contents.

In this chapter, you will build the functionality to access course contents, create a student registration system, and manage student enrollment onto courses. You will also learn how to cache data using the Django cache framework.

In this chapter, you will:

  • Create public views for displaying course information
  • Build a student registration system
  • Manage student enrollment onto courses
  • Render diverse content for course modules
  • Install and configure Memcached
  • Cache content using the Django cache framework
  • Use the Memcached and Redis cache backends
  • Monitor your Redis server in the Django administration site

Let’s start by creating a course catalog for students to browse existing courses and enroll on them.

The source code for this chapter can be found at https://github.com/PacktPublishing/Django-4-by-example/tree/main/Chapter14.

All Python modules used in this chapter are included in the requirements.txt file in the source code that comes along with this chapter. You can follow the instructions to install each Python module below or you can install all requirements at once with the command pip install -r requirements.txt.

Displaying courses

For your course catalog, you have to build the following functionalities:

  • List all available courses, optionally filtered by subject
  • Display a single course overview

Edit the views.py file of the courses application and add the following code:

from django.db.models import Count
from .models import Subject
class CourseListView(TemplateResponseMixin, View):
    model = Course
    template_name = 'courses/course/list.html'
    def get(self, request, subject=None):
        subjects = Subject.objects.annotate(
                       total_courses=Count('courses'))
        courses = Course.objects.annotate(
                       total_modules=Count('modules'))
        if subject:
            subject = get_object_or_404(Subject, slug=subject)
            courses = courses.filter(subject=subject)
        return self.render_to_response({'subjects': subjects,
                                        'subject': subject,
                                        'courses': courses})

This is the CourseListView view. It inherits from TemplateResponseMixin and View. In this view, you perform the following tasks:

  1. You retrieve all subjects, using the ORM’s annotate() method with the Count() aggregation function to include the total number of courses for each subject.
  2. You retrieve all available courses, including the total number of modules contained in each course.
  3. If a subject slug URL parameter is given, you retrieve the corresponding subject object and limit the query to the courses that belong to the given subject.
  4. You use the render_to_response() method provided by TemplateResponseMixin to render the objects to a template and return an HTTP response.

Let’s create a detail view for displaying a single course overview. Add the following code to the views.py file:

from django.views.generic.detail import DetailView
class CourseDetailView(DetailView):
    model = Course
    template_name = 'courses/course/detail.html'

This view inherits from the generic DetailView provided by Django. You specify the model and template_name attributes. Django’s DetailView expects a primary key (pk) or slug URL parameter to retrieve a single object for the given model. The view renders the template specified in template_name, including the Course object in the template context variable object.

Edit the main urls.py file of the educa project and add the following URL pattern to it:

from courses.views import CourseListView
urlpatterns = [
    # ...
    path('', CourseListView.as_view(), name='course_list'),
]

You add the course_list URL pattern to the main urls.py file of the project because you want to display the list of courses in the URL http://127.0.0.1:8000/, and all other URLs for the courses application have the /course/ prefix.

Edit the urls.py file of the courses application and add the following URL patterns:

path('subject/<slug:subject>/',
     views.CourseListView.as_view(),
     name='course_list_subject'),
path('<slug:slug>/',
     views.CourseDetailView.as_view(),
     name='course_detail'),

You define the following URL patterns:

  • course_list_subject: For displaying all courses for a subject
  • course_detail: For displaying a single course overview

Let’s build templates for the CourseListView and CourseDetailView views.

Create the following file structure inside the templates/courses/ directory of the courses application:

course/
    list.html
    detail.html

Edit the courses/course/list.html template of the courses application and write the following code:

{% extends "base.html" %}
{% block title %}
  {% if subject %}
    {{ subject.title }} courses
  {% else %}
    All courses
  {% endif %}
{% endblock %}
{% block content %}
  <h1>
    {% if subject %}
      {{ subject.title }} courses
    {% else %}
      All courses
    {% endif %}
  </h1>
  <div class="contents">
    <h3>Subjects</h3>
    <ul id="modules">
      <li {% if not subject %}class="selected"{% endif %}>
        <a href="{% url "course_list" %}">All</a>
      </li>
      {% for s in subjects %}
        <li {% if subject == s %}class="selected"{% endif %}>
          <a href="{% url "course_list_subject" s.slug %}">
            {{ s.title }}
            <br>
            <span>
              {{ s.total_courses }} course{{ s.total_courses|pluralize }} 
            </span>
          </a>
        </li>
      {% endfor %}
    </ul>
  </div>
  <div class="module">
    {% for course in courses %}
      {% with subject=course.subject %}
        <h3>
          <a href="{% url "course_detail" course.slug %}">
            {{ course.title }}
          </a>
        </h3>
        <p>
          <a href="{% url "course_list_subject" subject.slug %}">{{ subject }}</a>.
            {{ course.total_modules }} modules.
            Instructor: {{ course.owner.get_full_name }}
        </p>
      {% endwith %}
    {% endfor %}
  </div>
{% endblock %}

Make sure that no template tag is split into multiple lines.

This is the template for listing the available courses. You create an HTML list to display all Subject objects and build a link to the course_list_subject URL for each of them. You also include the total number of courses for each subject and use the pluralize template filter to add a plural suffix to the word course when the number is different than 1, to show 0 courses, 1 course, 2 courses, etc. You add a selected HTML class to highlight the current subject if a subject is selected. You iterate over every Course object, displaying the total number of modules and the instructor’s name.

Run the development server and open http://127.0.0.1:8000/ in your browser. You should see a page similar to the following one:

Figure 14.1: The course list page

The left sidebar contains all subjects, including the total number of courses for each of them. You can click any subject to filter the courses displayed.

Edit the courses/course/detail.html template and add the following code to it:

{% extends "base.html" %}
{% block title %}
  {{ object.title }}
{% endblock %}
{% block content %}
  {% with subject=object.subject %}
    <h1>
      {{ object.title }}
    </h1>
    <div class="module">
      <h2>Overview</h2>
      <p>
        <a href="{% url "course_list_subject" subject.slug %}">
        {{ subject.title }}</a>.
        {{ object.modules.count }} modules.
        Instructor: {{ object.owner.get_full_name }}
      </p>
      {{ object.overview|linebreaks }}
    </div>
  {% endwith %}
{% endblock %}

In this template, you display the overview and details for a single course. Open http://127.0.0.1:8000/ in your browser and click on one of the courses. You should see a page with the following structure:

Figure 14.2: The course overview page

You have created a public area for displaying courses. Next, you need to allow users to register as students and enroll on courses.

Adding student registration

Create a new application using the following command:

python manage.py startapp students

Edit the settings.py file of the educa project and add the new application to the INSTALLED_APPS setting, as follows:

INSTALLED_APPS = [
    # ...
    'students.apps.StudentsConfig',
]

Creating a student registration view

Edit the views.py file of the students application and write the following code:

from django.urls import reverse_lazy
from django.views.generic.edit import CreateView
from django.contrib.auth.forms import UserCreationForm
from django.contrib.auth import authenticate, login
class StudentRegistrationView(CreateView):
    template_name = 'students/student/registration.html'
    form_class = UserCreationForm
    success_url = reverse_lazy('student_course_list')
    def form_valid(self, form):
        result = super().form_valid(form)
        cd = form.cleaned_data
        user = authenticate(username=cd['username'],
                            password=cd['password1'])
        login(self.request, user)
        return result

This is the view that allows students to register on your site. You use the generic CreateView, which provides the functionality for creating model objects. This view requires the following attributes:

  • template_name: The path of the template to render this view.
  • form_class: The form for creating objects, which has to be ModelForm. You use Django’s UserCreationForm as the registration form to create User objects.
  • success_url: The URL to redirect the user to when the form is successfully submitted. You reverse the URL named student_course_list, which you are going to create in the Accessing the course contents section for listing the courses that students are enrolled on.

The form_valid() method is executed when valid form data has been posted. It has to return an HTTP response. You override this method to log the user in after they have successfully signed up.

Create a new file inside the students application directory and name it urls.py. Add the following code to it:

from django.urls import path
from . import views
urlpatterns = [
    path('register/',
         views.StudentRegistrationView.as_view(),
         name='student_registration'),
]

Then, edit the main urls.py of the educa project and include the URLs for the students application by adding the following pattern to your URL configuration:

urlpatterns = [
    # ...
    path('students/', include('students.urls')),
]

Create the following file structure inside the students application directory:

templates/
    students/
        student/
            registration.html

Edit the students/student/registration.html template and add the following code to it:

{% extends "base.html" %}
{% block title %}
  Sign up
{% endblock %}
{% block content %}
  <h1>
    Sign up
  </h1>
  <div class="module">
    <p>Enter your details to create an account:</p>
    <form method="post">
      {{ form.as_p }}
      {% csrf_token %}
      <p><input type="submit" value="Create my account"></p>
    </form>
  </div>
{% endblock %}

Run the development server and open http://127.0.0.1:8000/students/register/ in your browser. You should see a registration form like this:

Figure 14.3: The student registration form

Note that the student_course_list URL specified in the success_url attribute of the StudentRegistrationView view doesn’t exist yet. If you submit the form, Django won’t find the URL to redirect you to after a successful registration. As mentioned, you will create this URL in the Accessing the course contents section.

Enrolling on courses

After users create an account, they should be able to enroll on courses. To store enrollments, you need to create a many-to-many relationship between the Course and User models.

Edit the models.py file of the courses application and add the following field to the Course model:

students = models.ManyToManyField(User,
                                  related_name='courses_joined',
                                  blank=True)

From the shell, execute the following command to create a migration for this change:

python manage.py makemigrations

You will see output similar to this:

Migrations for 'courses':
  courses/migrations/0004_course_students.py
    - Add field students to course

Then, execute the next command to apply pending migrations:

python manage.py migrate

You should see output that ends with the following line:

Applying courses.0004_course_students... OK

You can now associate students with the courses on which they are enrolled. Let’s create the functionality for students to enroll on courses.

Create a new file inside the students application directory and name it forms.py. Add the following code to it:

from django import forms
from courses.models import Course
class CourseEnrollForm(forms.Form):
    course = forms.ModelChoiceField(
                 queryset=Course.objects.all(),
                 widget=forms.HiddenInput)

You are going to use this form for students to enroll on courses. The course field is for the course on which the user will be enrolled; therefore, it’s a ModelChoiceField. You use a HiddenInput widget because you are not going to show this field to the user. You are going to use this form in the CourseDetailView view to display a button to enroll.

Edit the views.py file of the students application and add the following code:

from django.views.generic.edit import FormView
from django.contrib.auth.mixins import LoginRequiredMixin
from .forms import CourseEnrollForm
class StudentEnrollCourseView(LoginRequiredMixin, 
                              FormView):
    course = None
    form_class = CourseEnrollForm
    def form_valid(self, form):
        self.course = form.cleaned_data['course']
        self.course.students.add(self.request.user)
        return super().form_valid(form)
    def get_success_url(self):
        return reverse_lazy('student_course_detail',
                            args=[self.course.id])

This is the StudentEnrollCourseView view. It handles students enrolling on courses. The view inherits from the LoginRequiredMixin mixin so that only logged-in users can access the view. It also inherits from Django’s FormView view, since you handle a form submission. You use the CourseEnrollForm form for the form_class attribute and also define a course attribute for storing the given Course object. When the form is valid, you add the current user to the students enrolled on the course.

The get_success_url() method returns the URL that the user will be redirected to if the form was successfully submitted. This method is equivalent to the success_url attribute. Then, you reverse the URL named student_course_detail.

Edit the urls.py file of the students application and add the following URL pattern to it:

path('enroll-course/',
     views.StudentEnrollCourseView.as_view(),
     name='student_enroll_course'),

Let’s add the enroll button form to the course overview page. Edit the views.py file of the courses application and modify CourseDetailView to make it look as follows:

from students.forms import CourseEnrollForm
class CourseDetailView(DetailView):
    model = Course
    template_name = 'courses/course/detail.html'
    def get_context_data(self, **kwargs):
        context = super().get_context_data(**kwargs)
        context['enroll_form'] = CourseEnrollForm(
                                   initial={'course':self.object})
        return context

You use the get_context_data() method to include the enrollment form in the context for rendering the templates. You initialize the hidden course field of the form with the current Course object so that it can be submitted directly.

Edit the courses/course/detail.html template and locate the following line:

{{ object.overview|linebreaks }}

Replace it with the following code:

{{ object.overview|linebreaks }}
{% if request.user.is_authenticated %}
  <form action="{% url "student_enroll_course" %}" method="post">
    {{ enroll_form }}
    {% csrf_token %}
    <input type="submit" value="Enroll now">
  </form>
{% else %}
  <a href="{% url "student_registration" %}" class="button">
    Register to enroll
  </a>
{% endif %}

This is the button for enrolling on courses. If the user is authenticated, you display the enrollment button, including the hidden form that points to the student_enroll_course URL. If the user is not authenticated, you display a link to register on the platform.

Make sure that the development server is running, open http://127.0.0.1:8000/ in your browser, and click a course. If you are logged in, you should see an ENROLL NOW button placed below the course overview, as follows:

Figure 14.4: The course overview page, including an ENROLL NOW button

If you are not logged in, you will see a REGISTER TO ENROLL button instead.

Accessing the course contents

You need a view for displaying the courses that students are enrolled on, and a view for accessing the actual course contents. Edit the views.py file of the students application and add the following code to it:

from django.views.generic.list import ListView
from courses.models import Course
class StudentCourseListView(LoginRequiredMixin, ListView):
    model = Course
    template_name = 'students/course/list.html'
    def get_queryset(self):
        qs = super().get_queryset()
        return qs.filter(students__in=[self.request.user])

This is the view to see courses that students are enrolled on. It inherits from LoginRequiredMixin to make sure that only logged-in users can access the view. It also inherits from the generic ListView for displaying a list of Course objects. You override the get_queryset() method to retrieve only the courses that a student is enrolled on; you filter the QuerySet by the student’s ManyToManyField field to do so.

Then, add the following code to the views.py file of the students application:

from django.views.generic.detail import DetailView
class StudentCourseDetailView(DetailView):
    model = Course
    template_name = 'students/course/detail.html'
    def get_queryset(self):
        qs = super().get_queryset()
        return qs.filter(students__in=[self.request.user])
    def get_context_data(self, **kwargs):
        context = super().get_context_data(**kwargs)
        # get course object
        course = self.get_object()
        if 'module_id' in self.kwargs:
            # get current module
            context['module'] = course.modules.get(
                id=self.kwargs['module_id'])
        else:
            # get first module
            context['module'] = course.modules.all()[0]
        return context

This is the StudentCourseDetailView view. You override the get_queryset() method to limit the base QuerySet to courses on which the student is enrolled. You also override the get_context_data() method to set a course module in the context if the module_id URL parameter is given. Otherwise, you set the first module of the course. This way, students will be able to navigate through modules inside a course.

Edit the urls.py file of the students application and add the following URL patterns to it:

path('courses/',
     views.StudentCourseListView.as_view(),
     name='student_course_list'),
path('course/<pk>/',
     views.StudentCourseDetailView.as_view(),
     name='student_course_detail'),
path('course/<pk>/<module_id>/',
     views.StudentCourseDetailView.as_view(),
     name='student_course_detail_module'),

Create the following file structure inside the templates/students/ directory of the students application:

course/
    detail.html
    list.html

Edit the students/course/list.html template and add the following code to it:

{% extends "base.html" %}
{% block title %}My courses{% endblock %}
{% block content %}
  <h1>My courses</h1>
  <div class="module">
    {% for course in object_list %}
      <div class="course-info">
        <h3>{{ course.title }}</h3>
        <p><a href="{% url "student_course_detail" course.id %}">
        Access contents</a></p>
      </div>
    {% empty %}
      <p>
        You are not enrolled in any courses yet.
        <a href="{% url "course_list" %}">Browse courses</a>
        to enroll on a course.
      </p>
    {% endfor %}
  </div>
{% endblock %}

This template displays the courses that the student is enrolled on. Remember that when a new student successfully registers with the platform, they will be redirected to the student_course_list URL. Let’s also redirect students to this URL when they log in to the platform.

Edit the settings.py file of the educa project and add the following code to it:

from django.urls import reverse_lazy
LOGIN_REDIRECT_URL = reverse_lazy('student_course_list')

This is the setting used by the auth module to redirect the student after a successful login if no next parameter is present in the request. After a successful login, a student will be redirected to the student_course_list URL to view the courses that they are enrolled on.

Edit the students/course/detail.html template and add the following code to it:

{% extends "base.html" %}
{% block title %}
  {{ object.title }}
{% endblock %}
{% block content %}
  <h1>
    {{ module.title }}
  </h1>
  <div class="contents">
    <h3>Modules</h3>
    <ul id="modules">
      {% for m in object.modules.all %}
        <li data-id="{{ m.id }}" {% if m == module %}class="selected"{% endif %}>
          <a href="{% url "student_course_detail_module" object.id m.id %}">
            <span>
              Module <span class="order">{{ m.order|add:1 }}</span>
            </span>
            <br>
            {{ m.title }}
          </a>
        </li>
      {% empty %}
        <li>No modules yet.</li>
      {% endfor %}
    </ul>
  </div>
  <div class="module">
    {% for content in module.contents.all %}
      {% with item=content.item %}
        <h2>{{ item.title }}</h2>
        {{ item.render }}
      {% endwith %}
    {% endfor %}
  </div>
{% endblock %}

Make sure no template tag is split across multiple lines. This is the template for enrolled students to access the contents of a course. First, you build an HTML list including all course modules and highlighting the current module. Then, you iterate over the current module contents and access each content item to display it using {{ item.render }}. You will add the render() method to the content models next. This method will take care of rendering the content properly.

You can now access http://127.0.0.1:8000/students/register/, register a new student account, and enroll on any course.

Rendering different types of content

To display the course contents, you need to render the different content types that you created: text, image, video, and file.

Edit the models.py file of the courses application and add the following render() method to the ItemBase model:

from django.template.loader import render_to_string
class ItemBase(models.Model):
    # ...
    def render(self):
        return render_to_string(
            f'courses/content/{self._meta.model_name}.html',
            {'item': self})

This method uses the render_to_string() function for rendering a template and returning the rendered content as a string. Each kind of content is rendered using a template named after the content model. You use self._meta.model_name to generate the appropriate template name for each content model dynamically. The render() method provides a common interface for rendering diverse content.

Create the following file structure inside the templates/courses/ directory of the courses application:

content/
    text.html
    file.html
    image.html
    video.html

Edit the courses/content/text.html template and write this code:

{{ item.content|linebreaks }}

This is the template to render text content. The linebreaks template filter replaces line breaks in plain text with HTML line breaks.

Edit the courses/content/file.html template and add the following:

<p>
  <a href="{{ item.file.url }}" class="button">Download file</a>
</p>

This is the template to render files. You generate a link to download the file.

Edit the courses/content/image.html template and write:

<p>
  <img src="{{ item.file.url }}" alt="{{ item.title }}">
</p>

This is the template to render images.

You also have to create a template for rendering Video objects. You will use django-embed-video for embedding video content. django-embed-video is a third-party Django application that allows you to embed videos in your templates, from sources such as YouTube or Vimeo, by simply providing their public URL.

Install the package with the following command:

pip install django-embed-video==1.4.4

Edit the settings.py file of your project and add the application to the INSTALLED_APPS setting, as follows:

INSTALLED_APPS = [
    # ...
    'embed_video',
]

You can find the django-embed-video application’s documentation at https://django-embed-video.readthedocs.io/en/latest/.

Edit the courses/content/video.html template and write the following code:

{% load embed_video_tags %}
{% video item.url "small" %}

This is the template to render videos.

Now, run the development server and access http://127.0.0.1:8000/course/mine/ in your browser. Access the site with a user that belongs to the Instructors group, and add multiple contents to a course. To include video content, you can just copy any YouTube URL, such as https://www.youtube.com/watch?v=bgV39DlmZ2U, and include it in the url field of the form.

After adding contents to the course, open http://127.0.0.1:8000/, click the course, and click on the ENROLL NOW button. You should be enrolled on the course and redirected to the student_course_detail URL. Figure 14.5 shows a sample course contents page:

Figure 14.5: A course contents page

Great! You have created a common interface for rendering courses with different types of content.

Using the cache framework

Processing HTTP requests to your web application usually entails database access, data manipulation, and template rendering. It is much more expensive in terms of processing than just serving a static website. The overhead in some requests can be significant when your site starts getting more and more traffic. This is where caching becomes precious. By caching queries, calculation results, or rendered content in an HTTP request, you will avoid expensive operations in the following requests that need to return the same data. This translates into shorter response times and less processing on the server side.

Django includes a robust cache system that allows you to cache data with different levels of granularity. You can cache a single query, the output of a specific view, parts of rendered template content, or your entire site. Items are stored in the cache system for a default time, but you can specify the timeout when you cache data.

This is how you will usually use the cache framework when your application processes an HTTP request:

  1. Try to find the requested data in the cache.
  2. If found, return the cached data.
  3. If not found, perform the following steps:
    1. Perform the database query or processing required to generate the data.
    2. Save the generated data in the cache.
    3. Return the data.

You can read detailed information about Django’s cache system at https://docs.djangoproject.com/en/4.1/topics/cache/.

Available cache backends

Django comes with the following cache backends:

  • backends.memcached.PyMemcacheCache or backends.memcached.PyLibMCCache: Memcached backends. Memcached is a fast and efficient memory-based cache server. The backend to use depends on the Memcached Python bindings you choose.
  • backends.redis.RedisCache: A Redis cache backend. This backend has been added in Django 4.0.
  • backends.db.DatabaseCache: Use the database as a cache system.
  • backends.filebased.FileBasedCache: Use the file storage system. This serializes and stores each cache value as a separate file.
  • backends.locmem.LocMemCache: A local memory cache backend. This is the default cache backend.
  • backends.dummy.DummyCache: A dummy cache backend intended only for development. It implements the cache interface without actually caching anything. This cache is per-process and thread-safe.

For optimal performance, use a memory-based cache backend such as the Memcached or Redis backends.

Installing Memcached

Memcached is a popular high-performance, memory-based cache server. We are going to use Memcached and the PyMemcacheCache Memcached backend.

Installing the Memcached Docker image

Run the following command from the shell to pull the Memcached Docker image:

docker pull memcached

This will download the Memcached Docker image to your local machine. If you don’t want to use Docker, you can also download Memcached from https://memcached.org/downloads.

Run the Memcached Docker container with the following command:

docker run -it --rm --name memcached -p 11211:11211 memcached -m 64

Memcached runs on port 11211 by default. The -p option is used to publish the 11211 port to the same host interface port. The -m option is used to limit the memory for the container to 64 MB. Memcached runs in memory, and it is allotted a specified amount of RAM. When the allotted RAM is full, Memcached starts removing the oldest data to store new data. If you want to run the command in detached mode (in the background of your terminal) you can use the -d option.

You can find more information about Memcached at https://memcached.org.

Installing the Memcached Python binding

After installing Memcached, you have to install a Memcached Python binding. We will install pymemcache, which is a fast, pure-Python Memcached client. Run the following command in the shell:

pip install pymemcache==3.5.2

You can read more information about the pymemcache library at https://github.com/pinterest/pymemcache.

Django cache settings

Django provides the following cache settings:

  • CACHES: A dictionary containing all available caches for the project.
  • CACHE_MIDDLEWARE_ALIAS: The cache alias to use for storage.
  • CACHE_MIDDLEWARE_KEY_PREFIX: The prefix to use for cache keys. Set a prefix to avoid key collisions if you share the same cache between several sites.
  • CACHE_MIDDLEWARE_SECONDS: The default number of seconds to cache pages.

The caching system for the project can be configured using the CACHES setting. This setting allows you to specify the configuration for multiple caches. Each cache included in the CACHES dictionary can specify the following data:

  • BACKEND: The cache backend to use.
  • KEY_FUNCTION: A string containing a dotted path to a callable that takes a prefix, version, and key as arguments and returns a final cache key.
  • KEY_PREFIX: A string prefix for all cache keys, to avoid collisions.
  • LOCATION: The location of the cache. Depending on the cache backend, this might be a directory, a host and port, or a name for the in-memory backend.
  • OPTIONS: Any additional parameters to be passed to the cache backend.
  • TIMEOUT: The default timeout, in seconds, for storing the cache keys. It is 300 seconds by default, which is 5 minutes. If set to None, cache keys will not expire.
  • VERSION: The default version number for the cache keys. Useful for cache versioning.

Adding Memcached to your project

Let’s configure the cache for your project. Edit the settings.py file of the educa project and add the following code to it:

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

You are using the PyMemcacheCache backend. You specify its location using the address:port notation. If you have multiple Memcached instances, you can use a list for LOCATION.

You have set up Memcached for your project. Let’s start caching data!

Cache levels

Django provides the following levels of caching, listed here by ascending order of granularity:

  • Low-level cache API: Provides the highest granularity. Allows you to cache specific queries or calculations.
  • Template cache: Allows you to cache template fragments.
  • Per-view cache: Provides caching for individual views.
  • Per-site cache: The highest-level cache. It caches your entire site.

Think about your cache strategy before implementing caching. Focus first on expensive queries or calculations that are not calculated on a per-user basis.

Let’s start by learning how to use the low-level cache API in your Python code.

Using the low-level cache API

The low-level cache API allows you to store objects in the cache with any granularity. It is located at django.core.cache. You can import it like this:

from django.core.cache import cache

This uses the default cache. It’s equivalent to caches['default']. Accessing a specific cache is also possible via its alias:

from django.core.cache import caches
my_cache = caches['alias']

Let’s take a look at how the cache API works. Open the Django shell with the following command:

python manage.py shell

Execute the following code:

>>> from django.core.cache import cache
>>> cache.set('musician', 'Django Reinhardt', 20)

You access the default cache backend and use set(key, value, timeout) to store a key named 'musician' with a value that is the string 'Django Reinhardt' for 20 seconds. If you don’t specify a timeout, Django uses the default timeout specified for the cache backend in the CACHES setting. Now, execute the following code:

>>> cache.get('musician')
'Django Reinhardt'

You retrieve the key from the cache. Wait for 20 seconds and execute the same code:

>>> cache.get('musician')

No value is returned this time. The 'musician' cache key has expired and the get() method returns None because the key is not in the cache anymore.

Always avoid storing a None value in a cache key because you won’t be able to distinguish between the actual value and a cache miss.

Let’s cache a QuerySet with the following code:

>>> from courses.models import Subject
>>> subjects = Subject.objects.all()
>>> cache.set('my_subjects', subjects)

You perform a QuerySet on the Subject model and store the returned objects in the 'my_subjects' key. Let’s retrieve the cached data:

>>> cache.get('my_subjects')
<QuerySet [<Subject: Mathematics>, <Subject: Music>, <Subject: Physics>, <Subject: Programming>]>

You are going to cache some queries in your views. Edit the views.py file of the courses application and add the following import:

from django.core.cache import cache

In the get() method of the CourseListView, find the following lines:

subjects = Subject.objects.annotate(
               total_courses=Count('courses'))

Replace the lines with the following ones:

subjects = cache.get('all_subjects')
if not subjects:
    subjects = Subject.objects.annotate(
                   total_courses=Count('courses'))
    cache.set('all_subjects', subjects)

In this code, you try to get the all_students key from the cache using cache.get(). This returns None if the given key is not found. If no key is found (not cached yet or cached but timed out), you perform the query to retrieve all Subject objects and their number of courses, and you cache the result using cache.set().

Checking cache requests with Django Debug Toolbar

Let’s add Django Debug Toolbar to the project to check the cache queries. You learned how to use Django Debug Toolbar in Chapter 7, Tracking User Actions.

First install Django Debug Toolbar with the following command:

pip install django-debug-toolbar==3.6.0

Edit the settings.py file of your project and add debug_toolbar to the INSTALLED_APPS setting as follows. The new line is highlighted in bold:

INSTALLED_APPS = [
    # ...
    'debug_toolbar',
]

In the same file, add the following line highlighted in bold to the MIDDLEWARE setting: 

MIDDLEWARE = [
    'debug_toolbar.middleware.DebugToolbarMiddleware',
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

Remember that DebugToolbarMiddleware has to be placed before any other middleware, except for middleware that encodes the response’s content, such as GZipMiddleware, which, if present, should come first.

Add the following lines at the end of the settings.py file:

INTERNAL_IPS = [
    '127.0.0.1',
]

Django Debug Toolbar will only display if your IP address matches an entry in the INTERNAL_IPS setting.

Edit the main urls.py file of the project and add the following URL pattern to urlpatterns:

path('__debug__/', include('debug_toolbar.urls')),]

Run the development server and open http://127.0.0.1:8000/ in your browser.

You should now see Django Debug Toolbar on the right side of the page. Click on Cache in the sidebar menu. You will see the following panel:

Figure 14.6: The Cache panel of Django Debug Toolbar including cache requests for CourseListView on a cache miss

Under Total calls you should see 2. The first time the CourseListView view is executed there are two cache requests. Under Commands you will see that the get command has been executed once, and that the set command has been executed once as well. The get command corresponds to the call that retrieves the all_subjects cache key. This is the first call displayed under Calls. The first time the view is executed a cache miss occurs because no data is cached yet. That’s why there is 1 under Cache misses. Then, the set command is used to store the results of the subjects QuerySet in the cache using the all_subjects cache key. This is the second call displayed under Calls.

In the SQL menu item of Django Debug Toolbar, you will see the total number of SQL queries executed in this request. This includes the query to retrieve all subjects that are then stored in the cache:

Figure 14.7: SQL queries executed for CourseListView on a cache miss

Reload the page in the browser and click on Cache in the sidebar menu:

Figure 14.8: The Cache panel of Django Debug Toolbar, including cache requests for CourseListView view on a cache hit

Now, there is only a single cache request. Under Total calls you should see 1. And under Commands you can see that the cache request corresponds to a get command. In this case there is a cache hit (see Cache hits) instead of a cache miss because the data has been found in the cache. Under Calls you can see the get request to retrieve the all_subjects cache key.

Check the SQL menu item of the debug toolbar. You should see that there is one less SQL query in this request. You are saving one SQL query because the view finds the data in the cache and doesn’t need to retrieve it from the database:

Figure 14.9: SQL queries executed for CourseListView on a cache hit

In this example, for a single request, it takes more time to retrieve the item from the cache than the time saved on the additional SQL query. However, when you have many users accessing your site, you will find significant time reductions by retrieving the data from the cache instead of hitting the database, and you will be able to serve the site to more concurrent users.

Successive requests to the same URL will retrieve the data from the cache. Since we didn’t specify a timeout when caching data with cache.set('all_subjects', subjects) in the CourseListView view, the default timeout will be used (300 seconds by default, which is 5 minutes). When the timeout is reached, the next request to the URL will generate a cache miss, the QuerySet will be executed, and data will be cached for another 5 minutes. You can define a different default timeout in the TIMEOUT element of the CACHES setting.

Caching based on dynamic data

Often, you will want to cache something that is based on dynamic data. In these cases, you have to build dynamic keys that contain all the information required to uniquely identify the cached data.

Edit the views.py file of the courses application and modify the CourseListView view to make it look like this:

class CourseListView(TemplateResponseMixin, View):
    model = Course
    template_name = 'courses/course/list.html'
    def get(self, request, subject=None):
        subjects = cache.get('all_subjects')
        if not subjects:
            subjects = Subject.objects.annotate(
                           total_courses=Count('courses'))
            cache.set('all_subjects', subjects)
        all_courses = Course.objects.annotate(
                           total_modules=Count('modules'))
        if subject:
            subject = get_object_or_404(Subject, slug=subject)
            key = f'subject_{subject.id}_courses'
            courses = cache.get(key)
            if not courses:
                courses = all_courses.filter(subject=subject)
                cache.set(key, courses)
        else:
            courses = cache.get('all_courses')
            if not courses:
                courses = all_courses
                cache.set('all_courses', courses)
        return self.render_to_response({'subjects': subjects,
                                        'subject': subject,
                                        'courses': courses})

In this case, you also cache both all courses and courses filtered by subject. You use the all_courses cache key for storing all courses if no subject is given. If there is a subject, you build the key dynamically with f'subject_{subject.id}_courses'.

It’s important to note that you can’t use a cached QuerySet to build other QuerySets, since what you cached are actually the results of the QuerySet. So you can’t do the following:

courses = cache.get('all_courses')
courses.filter(subject=subject)

Instead, you have to create the base QuerySet Course.objects.annotate(total_modules=Count('modules')), which is not going to be executed until it is forced, and use it to further restrict the QuerySet with all_courses.filter(subject=subject) in case the data was not found in the cache.

Caching template fragments

Caching template fragments is a higher-level approach. You need to load the cache template tags in your template using {% load cache %}. Then, you will be able to use the {% cache %} template tag to cache specific template fragments. You will usually use the template tag as follows:

{% cache 300 fragment_name %}
    ...
{% endcache %}

The {% cache %} template tag has two required arguments: the timeout in seconds and a name for the fragment. If you need to cache content depending on dynamic data, you can do so by passing additional arguments to the {% cache %} template tag to uniquely identify the fragment.

Edit the /students/course/detail.html of the students application. Add the following code at the top of it, just after the {% extends %} tag:

{% load cache %}

Then, find the following lines:

{% for content in module.contents.all %}
  {% with item=content.item %}
    <h2>{{ item.title }}</h2>
    {{ item.render }}
  {% endwith %}
{% endfor %}

Replace them with the following ones:

{% cache 600 module_contents module %}
  {% for content in module.contents.all %}
    {% with item=content.item %}
      <h2>{{ item.title }}</h2>
      {{ item.render }}
    {% endwith %}
  {% endfor %}
{% endcache %}

You cache this template fragment using the name module_contents and pass the current Module object to it. Thus, you uniquely identify the fragment. This is important to avoid caching a module’s contents and serving the wrong content when a different module is requested.

If the USE_I18N setting is set to True, the per-site middleware cache will respect the active language. If you use the {% cache %} template tag, you have to use one of the translation-specific variables available in templates to achieve the same result, such as {% cache 600 name request.LANGUAGE_CODE %}.

Caching views

You can cache the output of individual views using the cache_page decorator located at django.views.decorators.cache. The decorator requires a timeout argument (in seconds).

Let’s use it in your views. Edit the urls.py file of the students application and add the following import:

from django.views.decorators.cache import cache_page

Then, apply the cache_page decorator to the student_course_detail and student_course_detail_module URL patterns, as follows:

path('course/<pk>/',
     cache_page(60 * 15)(views.StudentCourseDetailView.as_view()),
     name='student_course_detail'),
path('course/<pk>/<module_id>/',
     cache_page(60 * 15)(views.StudentCourseDetailView.as_view()),
     name='student_course_detail_module'),

Now, the complete content returned by the StudentCourseDetailView is cached for 15 minutes.

The per-view cache uses the URL to build the cache key. Multiple URLs pointing to the same view will be cached separately.

Using the per-site cache

This is the highest-level cache. It allows you to cache your entire site. To allow the per-site cache, edit the settings.py file of your project and add the UpdateCacheMiddleware and FetchFromCacheMiddleware classes to the MIDDLEWARE setting, as follows:

MIDDLEWARE = [
    'debug_toolbar.middleware.DebugToolbarMiddleware',
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.cache.UpdateCacheMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.cache.FetchFromCacheMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

Remember that middleware is executed in the given order during the request phase, and in reverse order during the response phase. UpdateCacheMiddleware is placed before CommonMiddleware because it runs during response time, when middleware is executed in reverse order. FetchFromCacheMiddleware is placed after CommonMiddleware intentionally because it needs to access request data set by the latter.

Next, add the following settings to the settings.py file:

CACHE_MIDDLEWARE_ALIAS = 'default'
CACHE_MIDDLEWARE_SECONDS = 60 * 15  # 15 minutes
CACHE_MIDDLEWARE_KEY_PREFIX = 'educa'

In these settings, you use the default cache for your cache middleware and set the global cache timeout to 15 minutes. You also specify a prefix for all cache keys to avoid collisions in case you use the same Memcached backend for multiple projects. Your site will now cache and return cached content for all GET requests.

You can access the different pages and check the cache requests using Django Debug Toolbar. The per-site cache is not viable for many sites because it affects all views, even the ones that you might not want to cache, like management views where you want data to be returned from the database to reflect the latest changes.

In this project, the best approach is to cache the templates or views that are used to display course contents to students, while keeping the content management views for instructors without any cache.

Let’s deactivate the per-site cache. Edit the settings.py file of your project and comment out the UpdateCacheMiddleware and FetchFromCacheMiddleware classes in the MIDDLEWARE setting, as follows:

MIDDLEWARE = [
    'debug_toolbar.middleware.DebugToolbarMiddleware',
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    # 'django.middleware.cache.UpdateCacheMiddleware',
    'django.middleware.common.CommonMiddleware',
    # 'django.middleware.cache.FetchFromCacheMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

You have seen an overview of the different methods provided by Django to cache data. You should always define your cache strategy wisely, taking into account expensive QuerySets or calculations, data that won’t change frequently, and data that will be accessed concurrently by many users.

Using the Redis cache backend

Django 4.0 introduced a Redis cache backend. Let’s change the settings to use Redis instead of Memcached as the cache backend for the project. Remember that you already used Redis in Chapter 7, Tracking User Actions, and in Chapter 10, Extending Your Shop.

Install redis-py in your environment using the following command:

pip install redis==4.3.4

Then, edit the settings.py file of the educa project and modify the CACHES setting, as follows:

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.redis.RedisCache',
        'LOCATION': 'redis://127.0.0.1:6379',
    }
}

The project will now use the RedisCache cache backend. The location is defined in the format redis://[host]:[port]. You use 127.0.0.1 to point to the local host and 6379, which is the default port for Redis.

Initialize the Redis Docker container using the following command:

docker run -it --rm --name redis -p 6379:6379 redis

If you want to run the command in the background (in detached mode) you can use the -d option.

Run the development server and open http://127.0.0.1:8000/ in your browser. Check the cache requests in the Cache panel of Django Debug Toolbar. You are now using Redis as your project’s cache backend instead of Memcached.

Monitoring Redis with Django Redisboard

You can monitor your Redis server using Django Redisboard. Django Redisboard adds Redis statistics to the Django administration site. You can find more information about Django Redisboard at https://github.com/ionelmc/django-redisboard.

Install django-redisboard in your environment using the following command:

pip install django-redisboard==8.3.0

Install the attrs Python library used by django-redisboard in your environment with the following command:

pip install attrs

Edit the settings.py file of your project and add the application to the INSTALLED_APPS setting, as follows:

INSTALLED_APPS = [
    # ...
    'redisboard',
]

Run the following command from your project’s directory to run the Django Redisboard migrations:

python manage.py migrate redisboard

Run the development server and open http://127.0.0.1:8000/admin/redisboard/redisserver/add/ in your browser to add a Redis server to monitor. Under the Label, enter redis, and under URL, enter redis://localhost:6379/0, as in Figure 14.10:

Figure 14.10: The form to add a Redis server for Django Redisboard in the administration site

We will monitor the Redis instance running on our local host, which runs on port 6379 and uses the Redis database numbered 0. Click on SAVE. The information will be saved to the database, and you will be able to see the Redis configuration and metrics on the Django administration site:

Figure 14.11: The Redis monitoring of Django Redisboard on the administration site

Congratulations! You have successfully implemented caching for your project.

Additional resources

The following resources provide additional information related to the topics covered in this chapter:

Summary

In this chapter, you implemented the public views for the course catalog. You built a system for students to register and enroll on courses. You also created the functionality to render different types of content for the course modules. Finally, you learned how to use the Django cache framework and you used the Memcached and Redis cache backends for your project.

In the next chapter, you will build a RESTful API for your project using Django REST framework and consume it using the Python Requests library.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset