Event-driven architecture in FastAPI - Performance & Optimization

Performance: Event-driven architecture

MEDIUM IMPACT

This affects how quickly the application responds to user actions and external events, impacting interaction responsiveness and server load.

Handling user requests that trigger background tasks

FastAPI

from fastapi import FastAPI, BackgroundTasks
app = FastAPI()

@app.post('/process')
async def process_data(data: dict, background_tasks: BackgroundTasks):
    background_tasks.add_task(long_running_task, data)
    return {'status': 'processing started'}

def long_running_task(data):
    import time
    time.sleep(5)  # Simulates background work
    # Save results or notify user asynchronously

The long-running task runs in the background, allowing immediate response and freeing the event loop.

📈 Performance GainNon-blocking request handling, improves INP and server responsiveness

Handling user requests that trigger background tasks

FastAPI

from fastapi import FastAPI
app = FastAPI()

@app.post('/process')
async def process_data(data: dict):
    # Blocking call
    result = long_running_task(data)
    return {'result': result}

def long_running_task(data):
    import time
    time.sleep(5)  # Simulates blocking operation
    return 'done'

The long-running task blocks the request handler, delaying response and increasing server load.

📉 Performance CostBlocks event loop for 5 seconds, increasing INP and reducing throughput

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking synchronous task in request handler	N/A	N/A	N/A	[X] Bad
Background task with FastAPI BackgroundTasks	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Event-driven architecture offloads heavy or slow tasks from the main request-response cycle, reducing blocking in the server event loop and improving response times.

→Request Handling

→Event Loop

→Background Task Execution

⚠️ BottleneckBlocking synchronous operations in the main event loop

Core Web Vital Affected

INP

This affects how quickly the application responds to user actions and external events, impacting interaction responsiveness and server load.

Optimization Tips

1Avoid synchronous blocking operations in request handlers.

2Use FastAPI BackgroundTasks or external queues for heavy tasks.

3Keep the event loop free to maintain fast response times.

Performance Quiz - 3 Questions

What is the main performance benefit of using event-driven architecture in FastAPI?

A It reduces the size of the application bundle

B It improves CSS rendering speed

C It allows handling long tasks asynchronously without blocking requests

D It eliminates the need for a database

DevTools: Network and Performance panels

How to check: Use the Network panel to observe request response times. Use the Performance panel to record and analyze event loop blocking and task durations.

What to look for: Look for long request durations and event loop blocking time indicating synchronous blocking tasks.