Why advanced DRF features matter in Django - Performance Evidence

Performance: Why advanced DRF features matter

MEDIUM IMPACT

This affects API response time and server load, impacting how fast users get data and how well the server handles many requests.

Handling complex API data serialization and filtering

Django

from django_filters.rest_framework import DjangoFilterBackend
from rest_framework.pagination import PageNumberPagination

class MyViewSet(viewsets.ModelViewSet):
    queryset = MyModel.objects.all()
    serializer_class = MySerializer
    filter_backends = [DjangoFilterBackend]
    filterset_fields = ['status', 'category']
    pagination_class = PageNumberPagination

Filters and paginates data on the server, sending only needed data to clients quickly.

📈 Performance Gainresponse time reduced by 70% on large datasets; lower memory use

Handling complex API data serialization and filtering

Django

class MyViewSet(viewsets.ModelViewSet):
    queryset = MyModel.objects.all()
    serializer_class = MySerializer

    def get_queryset(self):
        return MyModel.objects.all()  # No filtering or optimization

Fetching all data without filtering or pagination causes slow responses and high server load.

📉 Performance Costblocks response for hundreds of ms on large datasets; high memory use

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No filtering or pagination	N/A (server-side)	N/A	N/A	[X] Bad
With filtering and pagination	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

DRF features affect the server-side data preparation before the browser rendering pipeline starts. Efficient queries and serialization reduce server response time, improving interaction speed.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (database queries and serialization)

Core Web Vital Affected

INP

This affects API response time and server load, impacting how fast users get data and how well the server handles many requests.

Optimization Tips

1Always use filtering to limit data returned by APIs.

2Use pagination to avoid sending large datasets at once.

3Optimize serializers to reduce processing time and payload size.

Performance Quiz - 3 Questions

How do advanced DRF features like filtering and pagination affect API performance?

A They reduce server load and speed up responses by limiting data sent.

B They increase server load by adding extra processing steps.

C They have no impact on performance.

D They only affect frontend rendering speed.

DevTools: Network

How to check: Open DevTools, go to Network tab, make API request, check response size and time.

What to look for: Look for smaller response payloads and faster response times indicating efficient DRF usage.

Practice

1. Why is it important to use advanced features like permissions in Django REST Framework (DRF)?

easy

A. To control who can access or modify API data

B. To speed up the server hardware

C. To change the database schema automatically

D. To make the API look prettier on the frontend

Solution

1. Step 1: Understand the role of permissions in DRF

   Permissions restrict or allow access to API endpoints based on user roles or authentication.

2. Step 2: Identify the purpose of permissions

   Permissions help keep data safe by controlling who can read or change it.

3. Final Answer:

   To control who can access or modify API data -> Option A

4. Quick Check:

   Permissions = Control access [OK]

Hint: Permissions control access rights in APIs [OK]

Common Mistakes:

• Thinking permissions improve server speed
• Confusing permissions with database changes
• Assuming permissions affect frontend design

2. Which of the following is the correct way to add pagination in a DRF viewset?

easy

A. pagination_class = PageNumberPagination

B. paginate = True

C. pagination = 'enabled'

D. page_size = 10

Solution

1. Step 1: Recall DRF pagination syntax

   DRF uses the attribute pagination_class to set pagination behavior in viewsets.

2. Step 2: Match the correct attribute and value

   Assigning PageNumberPagination to pagination_class enables page-based pagination.

3. Final Answer:

   pagination_class = PageNumberPagination -> Option A

4. Quick Check:

   Pagination uses pagination_class = PageNumberPagination [OK]

Hint: Use pagination_class to enable pagination in DRF [OK]

Common Mistakes:

• Using incorrect attribute names like paginate or pagination
• Setting page_size without pagination_class
• Assigning string values instead of classes

3. Given this DRF serializer method:

class MySerializer(serializers.ModelSerializer):
    def create(self, validated_data):
        user = self.context['request'].user
        validated_data['owner'] = user
        return super().create(validated_data)

What does this method do when creating an object?

medium

A. It raises an error because 'owner' is not in validated_data

B. It ignores the user and creates an anonymous object

C. It assigns the current user as the owner of the new object

D. It deletes the user from the request context

Solution

1. Step 1: Analyze the create method override

   The method adds the current user from the request context to the validated data under 'owner'.

2. Step 2: Understand the effect on object creation

   By adding 'owner', the created object will link to the user who made the request.

3. Final Answer:

   It assigns the current user as the owner of the new object -> Option C

4. Quick Check:

   create() adds user as owner [OK]

Hint: create() can add user info from context automatically [OK]

Common Mistakes:

• Assuming it raises error if 'owner' missing
• Thinking it deletes user from context
• Believing it ignores user data

4. You have this DRF viewset snippet:

class MyViewSet(viewsets.ModelViewSet):
    queryset = MyModel.objects.all()
    serializer_class = MySerializer
    permission_classes = [IsAuthenticated]

    def get_queryset(self):
        return MyModel.objects.filter(owner=self.request.user)

What is the main issue with this code?

medium

A. serializer_class must be a list, not a single class

B. permission_classes should be a tuple, not a list

C. get_queryset should not filter by owner

D. The queryset attribute is overridden by get_queryset, so it is redundant

Solution

1. Step 1: Understand get_queryset overriding

   Defining get_queryset replaces the queryset attribute for filtering dynamically.

2. Step 2: Identify redundancy

   Since get_queryset returns a filtered queryset, the class-level queryset is not used and is redundant.

3. Final Answer:

   The queryset attribute is overridden by get_queryset, so it is redundant -> Option D

4. Quick Check:

   get_queryset overrides queryset attribute [OK]

Hint: get_queryset overrides queryset attribute in viewsets [OK]

Common Mistakes:

• Thinking permission_classes must be a tuple
• Believing filtering by owner is wrong here
• Assuming serializer_class must be a list

5. You want to create a DRF API that returns a paginated list of items owned by the logged-in user, and automatically assigns the user as owner when creating new items. Which combination of features should you use?

hard

A. Use pagination_class only, without filtering or permissions

B. Use permission_classes to require login, override get_queryset to filter by user, use pagination_class, and override serializer create() to set owner

C. Use permission_classes to allow all, override get_queryset to return all items, and do not override create()

D. Use no permissions, set queryset to all items, disable pagination, and set owner manually in frontend

Solution

1. Step 1: Identify security and filtering needs

   Require login with permission_classes and filter queryset by logged-in user to show only their items.

2. Step 2: Add pagination and automatic owner assignment

   Use pagination_class to handle large data sets and override serializer create() to assign owner automatically.

3. Final Answer:

   Use permission_classes to require login, override get_queryset to filter by user, use pagination_class, and override serializer create() to set owner -> Option B

4. Quick Check:

   Permissions + filtering + pagination + create() override = D [OK]

Hint: Combine permissions, filtering, pagination, and create() override [OK]

Common Mistakes:

• Ignoring permissions and filtering
• Not using pagination for large data
• Setting owner only on frontend