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.

Practice

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

easy

A. It allows the app to react to actions immediately without waiting.

B. It makes the app run only on a single thread.

C. It requires no code to handle user requests.

D. It disables background tasks for faster response.

Solution

1. Step 1: Understand event-driven architecture

   Event-driven architecture lets the app respond to events as they happen, improving responsiveness.

2. Step 2: Connect to FastAPI's use of BackgroundTasks

   FastAPI uses BackgroundTasks to handle events without blocking the main user request, enabling immediate reactions.

3. Final Answer:

   It allows the app to react to actions immediately without waiting. -> Option A

4. Quick Check:

   Event-driven = Immediate reaction [OK]

Hint: Event-driven means reacting instantly to actions [OK]

Common Mistakes:

• Thinking event-driven means single-threaded only
• Believing no code is needed for requests
• Assuming background tasks are disabled

2. Which of the following is the correct way to import BackgroundTasks in FastAPI?

easy

A. import BackgroundTasks from fastapi

B. from fastapi.background import Tasks

C. from fastapi import BackgroundTasks

D. import fastapi.BackgroundTasks

Solution

1. Step 1: Recall FastAPI import syntax

   FastAPI uses standard Python import syntax: from module import class/function.

2. Step 2: Identify correct module and class

   The BackgroundTasks class is imported from fastapi directly, so the correct syntax is 'from fastapi import BackgroundTasks'.

3. Final Answer:

   from fastapi import BackgroundTasks -> Option C

4. Quick Check:

   Correct import syntax = from fastapi import BackgroundTasks [OK]

Hint: Use 'from fastapi import BackgroundTasks' to import correctly [OK]

Common Mistakes:

• Using wrong import order or syntax
• Trying to import from a non-existent submodule
• Using dot notation incorrectly in import

3. What will be the output when this FastAPI endpoint is called?

from fastapi import FastAPI, BackgroundTasks
app = FastAPI()

results = []

def write_log(message: str):
    results.append(message)

@app.post('/send')
async def send_message(background_tasks: BackgroundTasks):
    background_tasks.add_task(write_log, 'Message sent')
    return {'status': 'ok'}

# After calling POST /send once, what is the value of results?

medium

A. ['Message sent']

B. [] (empty list)

C. ['Message sent', 'Message sent']

D. Error: background_tasks not defined

Solution

1. Step 1: Understand BackgroundTasks behavior

   BackgroundTasks run after the response is sent, but in testing or immediate inspection, the task may not have run yet.

2. Step 2: Check when results list updates

   The results list is updated inside the background task, which runs asynchronously after returning the response, so immediately after the call, results is still empty.

3. Final Answer:

   [] (empty list) -> Option B

4. Quick Check:

   Background task runs after response = empty results [OK]

Hint: BackgroundTasks run after response, so immediate results stay empty [OK]

Common Mistakes:

• Assuming background task runs before return
• Expecting results updated synchronously
• Confusing background_tasks parameter usage

4. Identify the error in this FastAPI code using BackgroundTasks:

from fastapi import FastAPI, BackgroundTasks
app = FastAPI()

@app.post('/notify')
async def notify():
    background_tasks.add_task(print, 'Notify event')
    return {'message': 'Notification sent'}

medium

A. BackgroundTasks must be imported from fastapi.background module

B. print function cannot be used in background tasks

C. Missing await keyword before add_task call

D. background_tasks parameter missing in function definition

Solution

1. Step 1: Check function parameters for BackgroundTasks

   The function uses background_tasks but does not declare it as a parameter, so it is undefined inside the function.

2. Step 2: Confirm correct usage of BackgroundTasks

   BackgroundTasks must be accepted as a parameter in the endpoint function to be used, e.g., 'async def notify(background_tasks: BackgroundTasks)'.

3. Final Answer:

   background_tasks parameter missing in function definition -> Option D

4. Quick Check:

   Missing parameter = background_tasks parameter missing in function definition [OK]

Hint: Always add BackgroundTasks as a function parameter to use it [OK]

Common Mistakes:

• Forgetting to add background_tasks parameter
• Thinking print can't be used in background tasks
• Adding await to add_task (it's not a coroutine)

5. You want to send an email notification after a user registers without delaying the response. Which FastAPI pattern best fits this event-driven need?

hard

A. Use BackgroundTasks to send the email after returning the response

B. Send the email synchronously inside the endpoint before returning

C. Use a global variable to store emails and send later manually

D. Call the email function inside a separate thread without FastAPI support

Solution

1. Step 1: Understand the goal of non-blocking email sending

   We want the user to get a quick response while the email sends in the background.

2. Step 2: Match FastAPI's event-driven feature

   BackgroundTasks lets you schedule tasks to run after the response, perfect for sending emails without delay.

3. Final Answer:

   Use BackgroundTasks to send the email after returning the response -> Option A

4. Quick Check:

   BackgroundTasks = non-blocking post-response tasks [OK]

Hint: Use BackgroundTasks for post-response actions like emails [OK]

Common Mistakes:

• Sending email synchronously causing delay
• Using global variables for task management
• Manually managing threads without FastAPI support