Why middleware extends functionality in Flask - Performance Evidence

Performance: Why middleware extends functionality

MEDIUM IMPACT

Middleware affects request processing time and can impact server response speed and resource usage.

Adding functionality to handle requests in a Flask app

Flask

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

@app.before_request
def fast_middleware():
    g.start_time = 123  # Quick setup without delay

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

Middleware runs quickly without blocking, keeping response fast and user interactions smooth.

📈 Performance GainReduces request blocking time from 1 second to near zero, improving INP.

Adding functionality to handle requests in a Flask app

Flask

from flask import Flask
app = Flask(__name__)

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

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

Middleware blocks request processing with unnecessary delay, increasing response time.

📉 Performance CostBlocks response for 1 second per request, increasing INP and slowing user interaction.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Middleware with blocking delay	N/A (server-side)	N/A	N/A	[X] Bad
Lightweight, fast middleware	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Middleware runs during the server's request handling before the response is sent, adding processing steps that affect server response time.

→Request Handling

→Response Generation

⚠️ BottleneckRequest Handling stage is most expensive if middleware is slow or blocking.

Core Web Vital Affected

INP

Middleware affects request processing time and can impact server response speed and resource usage.

Optimization Tips

1Avoid blocking operations inside middleware to keep response fast.

2Use middleware only for necessary processing to minimize overhead.

3Test middleware impact using Network panel to monitor server response times.

Performance Quiz - 3 Questions

How does slow middleware affect user experience in a Flask app?

A It increases server response time, causing slower page loads.

B It reduces the size of the HTML sent to the browser.

C It improves browser rendering speed.

D It decreases network latency.

DevTools: Network

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

What to look for: Look for long waiting (TTFB) times indicating slow middleware processing.

Practice

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

easy

A. To add extra processing steps before or after the main app handles a request

B. To replace the Flask app's routing system

C. To directly modify the database schema

D. To serve static files like images and CSS

Solution

1. Step 1: Understand middleware role

   Middleware acts as a layer that processes requests or responses around the main app logic.

2. Step 2: Compare options

   Replacing routing, modifying database schema, or serving static files are not middleware tasks.

3. Final Answer:

   To add extra processing steps before or after the main app handles a request -> Option A

4. Quick Check:

   Middleware extends app functionality = C [OK]

Hint: Middleware adds steps around app requests and responses [OK]

Common Mistakes:

• Thinking middleware replaces routing
• Confusing middleware with static file serving
• Assuming middleware changes database structure

2. Which of the following is the correct way to add middleware in a Flask app?

easy

A. app = Middleware(app)

B. app.middleware = Middleware()

C. Middleware(app).run()

D. app.add_middleware(Middleware)

Solution

1. Step 1: Recall Flask middleware pattern

   Middleware wraps the Flask app by passing the app instance to the middleware constructor.

2. Step 2: Analyze options

   Only app = Middleware(app) correctly wraps the app instance. Others use invalid syntax or methods not in Flask.

3. Final Answer:

   app = Middleware(app) -> Option A

4. Quick Check:

   Middleware wraps app instance = A [OK]

Hint: Middleware wraps app like a gift box around it [OK]

Common Mistakes:

• Trying to assign middleware as an attribute
• Calling run() on middleware instead of app
• Using non-existent add_middleware method

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

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

app = SimpleMiddleware(app)

medium

A. No output printed

B. Only Before app printed

C. Only After app printed

D. Before app printed, then After app printed

Solution

1. Step 1: Understand __call__ method flow

   When a request comes, 'Before app' prints, then the wrapped app runs, then 'After app' prints.

2. Step 2: Confirm both prints execute

   Both print statements are before and after calling the app, so both appear in order.

3. Final Answer:

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

4. Quick Check:

   Middleware prints before and after app = A [OK]

Hint: Middleware prints before and after calling app [OK]

Common Mistakes:

• Thinking only one print runs
• Assuming prints happen in reverse order
• Forgetting __call__ runs on each request

4. This middleware code causes an error. What is the problem?

class BrokenMiddleware:
    def __init__(self, app):
        self.app = app
    def __call__(self, environ, start_response):
        # Forgot to call the wrapped app
        return 'Hello'

medium

A. Middleware must return a number, not a string

B. Middleware must call the wrapped app to return a valid response

C. Middleware should not have a __call__ method

D. Middleware __init__ method is missing

Solution

1. Step 1: Check __call__ method behavior

   The middleware returns a string directly without calling the wrapped app, breaking the request flow.

2. Step 2: Understand Flask middleware contract

   Middleware must call the wrapped app to get a valid response object, then return it.

3. Final Answer:

   Middleware must call the wrapped app to return a valid response -> Option B

4. Quick Check:

   Middleware must call app = D [OK]

Hint: Middleware must call wrapped app to work properly [OK]

Common Mistakes:

• Returning a string instead of calling app
• Missing __call__ method entirely
• Thinking middleware returns numbers

5. You want to add middleware that logs request paths and modifies the response to add a custom header. Which approach correctly extends functionality using middleware?

hard

A. Modify the Flask app routes to log and add headers directly inside each route function

B. Use middleware that only logs requests but does not call the app

C. Create middleware that logs environ['PATH_INFO'], calls the app, then adds header to response before returning

D. Add a middleware that replaces the response with a fixed string ignoring the app

Solution

1. Step 1: Understand middleware responsibilities

   Middleware should handle logging before calling the app and modify the response after.

2. Step 2: Evaluate options

   Create middleware that logs environ['PATH_INFO'], calls the app, then adds header to response before returning correctly logs the request path, calls the app, then modifies the response headers. Others either bypass app or do tasks incorrectly.

3. Final Answer:

   Create middleware that logs environ['PATH_INFO'], calls the app, then adds header to response before returning -> Option C

4. Quick Check:

   Middleware logs and modifies response = B [OK]

Hint: Middleware wraps app: log before, modify response after [OK]

Common Mistakes:

• Modifying routes instead of middleware
• Not calling the wrapped app
• Replacing response ignoring app output