Custom middleware creation in Flask - Performance & Optimization

Performance: Custom middleware creation

MEDIUM IMPACT

This affects the request-response cycle speed and server processing time, impacting how fast the server can respond to user requests.

Adding custom middleware to process requests in Flask

Flask

from flask import Flask, request
app = Flask(__name__)

@app.before_request
def fast_middleware():
    # Quick check without blocking
    if 'X-Special-Header' not in request.headers:
        pass  # Minimal processing

@app.route('/')
def index():
    return 'Hello World!'

Middleware runs quickly without blocking, allowing fast request handling and better throughput.

📈 Performance GainReduces request blocking time from 2 seconds to near zero, improving server responsiveness.

Adding custom middleware to process requests in Flask

Flask

from flask import Flask, request
app = Flask(__name__)

@app.before_request
def slow_middleware():
    import time
    time.sleep(2)  # Simulate slow processing

@app.route('/')
def index():
    return 'Hello World!'

This middleware blocks every request for 2 seconds, delaying response and increasing server load.

📉 Performance CostBlocks request processing for 2 seconds per request, increasing server response time significantly.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking middleware with sleep	0	0	0	[X] Bad
Lightweight middleware with quick checks	0	0	0	[OK] Good

Rendering Pipeline

Middleware runs on the server before the response is sent. It affects server processing time but does not directly impact browser rendering stages.

→Server Request Processing

⚠️ BottleneckMiddleware that blocks or performs heavy computation delays the entire request-response cycle.

Optimization Tips

1Avoid blocking operations like sleep or heavy computation in middleware.

2Keep middleware logic simple and fast to reduce server response delays.

3Use DevTools Network tab to monitor server response times and detect middleware bottlenecks.

Performance Quiz - 3 Questions

What is the main performance risk of a custom middleware that uses time.sleep() in Flask?

A It increases CSS selector complexity.

B It causes browser layout shifts.

C It blocks the request processing, increasing server response time.

D It reduces bundle size.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the Time column for server response delays.

What to look for: Look for high 'Waiting (TTFB)' times indicating slow server response caused by middleware.

Practice

1. What is the main purpose of creating custom middleware in a Flask application?

easy

A. To run code before and after each request is processed by Flask

B. To define new routes and views in the Flask app

C. To replace Flask's built-in request handling completely

D. To create database models for the application

Solution

1. Step 1: Understand middleware role

   Middleware runs code around request processing, before and after Flask handles requests.

2. Step 2: Compare options

   Only To run code before and after each request is processed by Flask describes this behavior. Other options describe unrelated tasks.

3. Final Answer:

   To run code before and after each request is processed by Flask -> Option A

4. Quick Check:

   Middleware purpose = run code around requests [OK]

Hint: Middleware wraps requests to add extra processing [OK]

Common Mistakes:

• Confusing middleware with route creation
• Thinking middleware replaces Flask core
• Mixing middleware with database models

2. Which of the following is the correct way to define a custom middleware class in Flask?

easy

A. class MyMiddleware:
def __init__(self, app):
self.app = app
def __call__(self, environ, start_response):
return self.app(environ, start_response)

B. def MyMiddleware(app):
return app

C. class MyMiddleware:
def handle_request(self):
pass

D. class MyMiddleware:
def __init__(self):
pass

Solution

1. Step 1: Check middleware class structure

   Middleware must accept the app in __init__ and implement __call__ with environ and start_response.

2. Step 2: Validate options

   Only class MyMiddleware: def __init__(self, app): self.app = app def __call__(self, environ, start_response): return self.app(environ, start_response) matches this pattern correctly. Others miss __call__ or parameters.

3. Final Answer:

   Correct middleware class with __init__ and __call__ methods -> Option A

4. Quick Check:

   Middleware class needs __call__ method [OK]

Hint: Middleware class must implement __call__(environ, start_response) [OK]

Common Mistakes:

• Omitting __call__ method
• Not passing app to __init__
• Using function instead of class

3. Given this middleware code, what will be printed when a request is made?

class LoggerMiddleware:
    def __init__(self, app):
        self.app = app
    def __call__(self, environ, start_response):
        print('Before request')
        response = self.app(environ, start_response)
        print('After request')
        return response

app.wsgi_app = LoggerMiddleware(app.wsgi_app)

medium

A. Only After request printed

B. Only Before request printed

C. No output printed

D. Before request printed, then After request printed

Solution

1. Step 1: Analyze __call__ method

   Prints 'Before request', calls app, then prints 'After request'.

2. Step 2: Understand call order

   Both prints happen on each request, before and after app call.

3. Final Answer:

   Before request printed, then After request printed -> Option D

4. Quick Check:

   Prints before and after app call [OK]

Hint: Middleware __call__ runs code before and after app call [OK]

Common Mistakes:

• Thinking only one print runs
• Confusing order of prints
• Assuming prints happen outside __call__

4. Identify the error in this middleware code snippet:

class BadMiddleware:
    def __init__(self, app):
        self.app = app
    def __call__(self, request):
        print('Middleware active')
        return self.app(request)

medium

A. Missing __init__ method to accept app

B. __call__ method has wrong parameters; should be (environ, start_response)

C. Middleware class should not print anything

D. The return statement should be outside __call__

Solution

1. Step 1: Check __call__ method signature

   WSGI middleware __call__ must accept (environ, start_response), not (request).

2. Step 2: Validate other parts

   __init__ is correct, printing is allowed, return inside __call__ is correct.

3. Final Answer:

   __call__ method has wrong parameters; should be (environ, start_response) -> Option B

4. Quick Check:

   Middleware __call__ signature = (environ, start_response) [OK]

Hint: Middleware __call__ needs environ and start_response params [OK]

Common Mistakes:

• Using Flask request object instead of WSGI params
• Omitting start_response parameter
• Misplacing return statement

5. You want to create middleware that adds a custom header 'X-Hello: World' to every response. Which code snippet correctly implements this?

hard

A. class HeaderMiddleware:
def __init__(self, app):
self.app = app
def __call__(self, environ, start_response):
response = self.app(environ, start_response)
response.headers['X-Hello'] = 'World'
return response

B. class HeaderMiddleware:
def __init__(self, app):
self.app = app
def __call__(self, environ, start_response):
start_response('200 OK', [('X-Hello', 'World')])
return self.app(environ, start_response)

C. class HeaderMiddleware:
def __init__(self, app):
self.app = app
def __call__(self, environ, start_response):
def custom_start_response(status, headers, exc_info=None):
headers.append(('X-Hello', 'World'))
return start_response(status, headers, exc_info)
return self.app(environ, custom_start_response)

D. class HeaderMiddleware:
def __init__(self, app):
self.app = app
def __call__(self, environ, start_response):
environ['X-Hello'] = 'World'
return self.app(environ, start_response)

Solution

1. Step 1: Understand WSGI header modification

   Headers are set by calling start_response with status and headers. To add headers, wrap start_response.

2. Step 2: Check options for correct header addition

   class HeaderMiddleware: def __init__(self, app): self.app = app def __call__(self, environ, start_response): def custom_start_response(status, headers, exc_info=None): headers.append(('X-Hello', 'World')) return start_response(status, headers, exc_info) return self.app(environ, custom_start_response) wraps start_response to append header before calling original start_response. Others misuse start_response or response object.

3. Final Answer:

   Wrap start_response to add header before calling original -> Option C

4. Quick Check:

   Add headers by wrapping start_response [OK]

Hint: Wrap start_response to add headers in middleware [OK]

Common Mistakes:

• Calling start_response twice incorrectly
• Trying to modify response object directly in WSGI
• Adding headers to environ instead of response