Lifespan context manager in FastAPI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the lifespan context manager in FastAPI?

It manages startup and shutdown events for the application, allowing you to run code before the app starts and after it stops.

intermediate

How do you define a lifespan context manager in FastAPI?

By creating an async generator function that yields control once startup tasks are done, then runs shutdown tasks after the yield.

beginner

Which FastAPI parameter accepts the lifespan context manager?

The 'lifespan' parameter in the FastAPI constructor accepts the lifespan context manager function.

intermediate

What happens if you don't use a lifespan context manager in FastAPI?

You cannot run custom startup or shutdown code automatically; you would need to use event decorators or miss lifecycle control.

beginner

Show a simple example of a lifespan context manager in FastAPI.

from fastapi import FastAPI
from contextlib import asynccontextmanager

@asynccontextmanager
async def lifespan(app):
    print('Starting up')
    yield
    print('Shutting down')

app = FastAPI(lifespan=lifespan)

What type of function is used to create a lifespan context manager in FastAPI?

A A regular synchronous function

B An async generator function

C A class constructor

D A lambda function

The lifespan context manager must be an async generator function that yields control to manage startup and shutdown.

Where do you pass the lifespan context manager in FastAPI?

A As the 'lifespan' argument in FastAPI()

B Inside a route decorator

C In the middleware configuration

D In the database connection setup

You pass the lifespan context manager function as the 'lifespan' parameter when creating the FastAPI app instance.

What does the yield statement do inside the lifespan context manager?

A Starts the server

B Ends the function immediately

C Pauses startup and waits for shutdown

D Runs the main application code

The yield pauses the startup code and lets FastAPI run the app; after the app stops, the code after yield runs for shutdown.

Which of these is NOT a benefit of using a lifespan context manager?

A Faster HTTP response times

B Centralized startup and shutdown logic

C Automatic resource cleanup

D Cleaner code organization

Lifespan context managers help with startup/shutdown tasks, not directly with HTTP response speed.

If you want to connect to a database on startup and disconnect on shutdown, where should you put this code?

A In the main.py global scope

B Inside a route handler

C In the HTML templates

D Inside the lifespan context manager

The lifespan context manager is the right place to open and close resources like database connections.

Explain how the lifespan context manager controls startup and shutdown in FastAPI.

Think about what happens before and after the yield in the async function.

Describe a real-life scenario where using a lifespan context manager in FastAPI is helpful.

Imagine preparing and cleaning up before and after a big event.