Async middleware in Django - Performance & Optimization

Performance: Async middleware

MEDIUM IMPACT

Async middleware affects server request handling speed and responsiveness, impacting how fast pages start loading for users.

Handling HTTP requests with middleware that performs I/O operations

Django

def middleware(get_response):
    async def middleware_func(request):
        # Non-blocking async I/O
        result = await async_io_call()
        response = await get_response(request)
        return response
    return middleware_func

Async middleware releases the server thread during I/O, allowing other requests to be handled concurrently.

📈 Performance GainImproves server concurrency and reduces request wait time

Handling HTTP requests with middleware that performs I/O operations

Django

def middleware(get_response):
    def middleware_func(request):
        # Blocking I/O operation
        result = blocking_io_call()
        response = get_response(request)
        return response
    return middleware_func

Blocking I/O in sync middleware holds the server thread, delaying response and reducing concurrency.

📉 Performance CostBlocks server thread, increasing response time and reducing throughput

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Sync middleware with blocking I/O	N/A (server-side)	N/A	N/A	[X] Bad
Async middleware with awaitable I/O	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Async middleware runs during the server's request handling before the response is sent. It affects how quickly the server can start sending content to the browser.

→Request Handling

→Response Generation

⚠️ BottleneckBlocking I/O in middleware delays response start, increasing LCP

Core Web Vital Affected

LCP

Async middleware affects server request handling speed and responsiveness, impacting how fast pages start loading for users.

Optimization Tips

1Avoid blocking I/O calls inside middleware to prevent server thread blocking.

2Use async middleware with awaitable calls to improve server concurrency.

3Faster server responses from async middleware reduce LCP and improve user experience.

Performance Quiz - 3 Questions

What is the main performance benefit of using async middleware in Django?

A It allows the server to handle other requests while waiting for I/O operations.

B It reduces the size of the middleware code.

C It improves client-side rendering speed directly.

D It caches all responses automatically.

DevTools: Network

How to check: Open DevTools Network tab, reload the page, and check the Time to First Byte (TTFB) and response times.

What to look for: Lower TTFB and faster response times indicate efficient async middleware handling.

Practice

1. What is the main benefit of using async middleware in Django?

easy

A. It allows Django to handle requests without waiting, improving speed.

B. It automatically caches all responses for faster loading.

C. It replaces the need for database queries.

D. It disables middleware for static files.

Solution

1. Step 1: Understand async middleware purpose

   Async middleware lets Django process requests without blocking, so it can handle other tasks simultaneously.

2. Step 2: Compare options

   Only It allows Django to handle requests without waiting, improving speed. correctly describes this benefit. Options A, C, and D describe unrelated or incorrect behaviors.

3. Final Answer:

   It allows Django to handle requests without waiting, improving speed. -> Option A

4. Quick Check:

   Async middleware improves speed by non-blocking handling [OK]

Hint: Async means non-blocking, so it improves request handling speed [OK]

Common Mistakes:

• Thinking async middleware caches responses
• Confusing async middleware with database optimization
• Assuming async disables middleware for static files

2. Which of the following is the correct way to define an async middleware __call__ method in Django?

easy

A. async def __call__(self, request): response = await self.get_response(request); return response

B. def __call__(self, request): response = await self.get_response(request); return response

C. def __call__(self, request): return self.get_response(request)

D. async def __call__(self, request): return self.get_response(request)

Solution

1. Step 1: Identify async method syntax

   The method must be declared with async def to use await inside.

2. Step 2: Check usage of await

   Only async def __call__(self, request): response = await self.get_response(request); return response correctly uses await with self.get_response(request) inside an async method.

3. Final Answer:

   async def __call__(self, request): response = await self.get_response(request); return response -> Option A

4. Quick Check:

   Async method with await = async def __call__(self, request): response = await self.get_response(request); return response [OK]

Hint: Async methods need async def and await inside [OK]

Common Mistakes:

• Using await inside a non-async function
• Missing await when calling async get_response
• Defining __call__ without async keyword

3. Given this async middleware snippet, what will be printed when a request is processed?

class LogMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    async def __call__(self, request):
        print('Before response')
        response = await self.get_response(request)
        print('After response')
        return response

medium

A. No output printed due to async

B. Only Before response printed, then returns

C. Only After response printed, then returns

D. Before response printed, then After response printed after response

Solution

1. Step 1: Analyze print statements order

   The middleware prints 'Before response' before awaiting the response, then prints 'After response' after awaiting.

2. Step 2: Understand async call flow

   Await pauses until response is ready, so both prints happen in order around the response.

3. Final Answer:

   Before response printed, then After response printed after response -> Option D

4. Quick Check:

   Print before and after await = Before response printed, then After response printed after response [OK]

Hint: Print before and after await shows both messages in order [OK]

Common Mistakes:

• Thinking async prevents print output
• Assuming only one print runs
• Confusing order of prints around await

4. Identify the error in this async middleware code:

class HeaderMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    async def __call__(self, request):
        response = self.get_response(request)
        response['X-Custom'] = 'Value'
        return response

medium

A. Async __call__ cannot return response

B. Cannot modify response headers in middleware

C. Missing await before self.get_response(request)

D. Missing async keyword in __init__

Solution

1. Step 1: Check async call to get_response

   Since __call__ is async, get_response must be awaited if it returns a coroutine.

2. Step 2: Identify missing await

   The code calls self.get_response(request) without await, causing a coroutine object instead of response.

3. Final Answer:

   Missing await before self.get_response(request) -> Option C

4. Quick Check:

   Async call needs await before get_response [OK]

Hint: Await async calls inside async methods [OK]

Common Mistakes:

• Forgetting await on async get_response
• Thinking response headers can't be changed
• Adding async to __init__ method

5. You want to create async middleware that adds a custom header only if the response status is 200. Which code snippet correctly implements this?

hard

A. async def __call__(self, request):
response = await self.get_response(request)
response['X-Status'] = 'OK'
return response

B. async def __call__(self, request):
response = await self.get_response(request)
if response.status_code == 200:
response['X-Status'] = 'OK'
return response

C. async def __call__(self, request):
response = self.get_response(request)
if response.status_code == 200:
response['X-Status'] = 'OK'
return response

D. def __call__(self, request):
response = self.get_response(request)
if response.status_code == 200:
response['X-Status'] = 'OK'
return response

Solution

1. Step 1: Confirm async __call__ and await usage

   The method must be async and await the get_response call to get the response object.

2. Step 2: Check conditional header addition

   Only async def __call__(self, request): response = await self.get_response(request) if response.status_code == 200: response['X-Status'] = 'OK' return response adds the header conditionally when status_code is 200, matching the requirement.

3. Final Answer:

   async def __call__(self, request): response = await self.get_response(request); if response.status_code == 200: response['X-Status'] = 'OK'; return response -> Option B

4. Quick Check:

   Async call with await and conditional header = async def __call__(self, request): response = await self.get_response(request) if response.status_code == 200: response['X-Status'] = 'OK' return response [OK]

Hint: Use async def with await and check status before adding header [OK]

Common Mistakes:

• Not awaiting get_response in async method
• Adding header unconditionally
• Defining __call__ as sync when async needed