Event-driven architecture in FastAPI

Introduction

Event-driven architecture helps your app react to actions or changes instantly. It makes your app more flexible and easier to manage by focusing on events.

You want your FastAPI app to respond immediately when a user uploads a file.

You need to trigger background tasks after a user submits a form.

Your app should update other parts automatically when data changes.

You want to decouple parts of your app so they work independently.

You want to handle notifications or logs when certain actions happen.

Syntax

FastAPI

from fastapi import FastAPI
from fastapi import BackgroundTasks

app = FastAPI()

@app.post("/items/")
async def create_item(item: dict, background_tasks: BackgroundTasks):
    background_tasks.add_task(process_item, item)
    return {"message": "Item received"}

def process_item(item: dict):
    # handle the event here
    print(f"Processing item: {item}")

Use BackgroundTasks to run functions after the main request finishes.

Define event handlers as normal functions and add them to background tasks.

Examples

This example sends a welcome email after the API call finishes.

FastAPI

from fastapi import FastAPI, BackgroundTasks

app = FastAPI()

@app.post("/send-email/")
async def send_email(background_tasks: BackgroundTasks):
    background_tasks.add_task(send_welcome_email)
    return {"message": "Email will be sent"}

def send_welcome_email():
    print("Sending welcome email...")

This example logs user actions to a file without delaying the response.

FastAPI

from fastapi import FastAPI, BackgroundTasks

app = FastAPI()

@app.post("/log-action/")
async def log_action(action: str, background_tasks: BackgroundTasks):
    background_tasks.add_task(log_to_file, action)
    return {"message": "Action logged"}

def log_to_file(action: str):
    with open("actions.log", "a") as f:
        f.write(f"Action: {action}\n")

Sample Program

This FastAPI app accepts data and immediately returns a response. Meanwhile, it processes the data in the background as an event.

FastAPI

from fastapi import FastAPI, BackgroundTasks
from fastapi.responses import JSONResponse

app = FastAPI()

@app.post("/process-data/")
async def process_data(data: dict, background_tasks: BackgroundTasks):
    background_tasks.add_task(handle_event, data)
    return JSONResponse(content={"status": "Data received"})

def handle_event(data: dict):
    print(f"Event received with data: {data}")
    # Imagine processing or notifying other services here

Important Notes

Background tasks run after the response is sent, so users don't wait.

Use event-driven design to keep your app responsive and scalable.

FastAPI's BackgroundTasks is a simple way to start with event-driven patterns.

Summary

Event-driven architecture lets your app react to actions as they happen.

FastAPI uses BackgroundTasks to handle events without blocking users.

This approach makes your app faster and easier to maintain.

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