Event-driven architecture in FastAPI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is event-driven architecture in FastAPI?

Event-driven architecture is a design where components communicate by sending and reacting to events asynchronously, allowing FastAPI apps to handle tasks like notifications or background jobs efficiently.

intermediate

How does FastAPI support event-driven programming?

FastAPI supports event-driven programming using background tasks, WebSocket endpoints, and integration with message brokers like Redis or RabbitMQ to handle events asynchronously.

beginner

What is a background task in FastAPI?

A background task in FastAPI is a function that runs after returning a response, letting the app handle long-running jobs without blocking the user's request.

intermediate

Why use message brokers in event-driven FastAPI apps?

Message brokers like Redis or RabbitMQ help FastAPI apps send, queue, and receive events between services reliably and asynchronously, improving scalability and decoupling components.

beginner

Give an example of an event-driven use case in FastAPI.

An example is sending a welcome email after user signup using a background task or publishing a 'user_created' event to a message broker for other services to react.

Which FastAPI feature allows running code after sending a response without blocking the user?

A Background tasks

B Synchronous endpoints

C Middleware

D Static files

Background tasks run after the response is sent, letting FastAPI handle long jobs without blocking.

In event-driven architecture, components communicate by:

A Calling each other directly

B Sending and reacting to events

C Sharing a global variable

D Using synchronous functions only

Event-driven architecture uses events to communicate asynchronously between components.

Which of these is a common message broker used with FastAPI for event-driven apps?

A RabbitMQ

B SQLite

C Flask

D CSS

RabbitMQ is a popular message broker for sending and receiving events asynchronously.

What role do WebSockets play in FastAPI's event-driven architecture?

A Replace background tasks

B Serve static files

C Enable real-time two-way communication

D Manage database migrations

WebSockets allow real-time, two-way communication, useful for event-driven features like chat.

Why is event-driven architecture good for scalability?

A It tightly couples components

B It requires fewer servers

C It processes events synchronously

D It decouples components and handles tasks asynchronously

Decoupling and asynchronous processing help apps scale better under load.

Explain how FastAPI can implement event-driven architecture using background tasks and message brokers.

Think about how tasks can run without blocking and how events can be sent between services.

Describe a real-life example where event-driven architecture in FastAPI improves user experience.

Imagine what happens after a user signs up on a website.

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