Database session management in FastAPI - Performance & Optimization

Performance: Database session management

HIGH IMPACT

This affects backend response time and frontend loading speed by controlling how database connections are opened, reused, and closed during API requests.

Managing database connections per API request

FastAPI

from fastapi import Depends
from sqlalchemy.orm import Session

# Use connection pooling configured in SessionLocal

def get_db():
    db = SessionLocal()
    try:
        yield db
    finally:
        db.close()

@app.get("/items/")
def read_items(db: Session = Depends(get_db)):
    return db.query(Item).all()

Using connection pooling inside SessionLocal reuses existing connections, reducing overhead per request.

📈 Performance Gainreduces latency by 30-40ms per request, improving LCP

Managing database connections per API request

FastAPI

def get_db():
    db = SessionLocal()
    try:
        yield db
    finally:
        db.close()

@app.get("/items/")
def read_items(db: Session = Depends(get_db)):
    return db.query(Item).all()

Creating and closing a new database session for every single request causes overhead and delays, especially under high load.

📉 Performance Costadds 10-50ms latency per request due to connection setup and teardown

Performance Comparison

Pattern	DB Connections	Latency Impact	Concurrency	Verdict
New session per request without pooling	Creates new connection each time	High latency (10-50ms extra)	Poor concurrency due to overhead	[X] Bad
Global session reused across requests	Single connection reused	Low latency but risk of stale data	Blocks concurrent requests	[X] Bad
Scoped session with connection pooling	Reuses pooled connections	Low latency (~5-10ms overhead)	Good concurrency and fresh data	[OK] Good

Rendering Pipeline

Database session management impacts the backend response time, which affects when the browser receives data to render the page.

→Backend Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckBackend Processing (database query latency)

Core Web Vital Affected

LCP

This affects backend response time and frontend loading speed by controlling how database connections are opened, reused, and closed during API requests.

Optimization Tips

1Always use connection pooling to reuse database connections.

2Create and close database sessions scoped to each request.

3Avoid global or long-lived database sessions to prevent blocking.

Performance Quiz - 3 Questions

What is the main performance benefit of using connection pooling in FastAPI database sessions?

A It caches query results on the client side.

B It reduces the number of new database connections created per request.

C It eliminates the need for database sessions entirely.

D It delays closing database connections until server shutdown.

DevTools: Network

How to check: Open DevTools > Network tab, reload the page, and check the Time and Waiting (TTFB) columns for API calls.

What to look for: Look for long server response times indicating slow database queries or connection overhead.

Practice

1. What is the main purpose of using a get_db function in FastAPI when working with databases?

easy

A. To create and close a database session for each request safely

B. To store user data permanently in memory

C. To handle HTTP requests directly without a database

D. To generate HTML templates for responses

Solution

1. Step 1: Understand the role of get_db

   The get_db function is designed to open a database session when a request starts and close it when the request ends.

2. Step 2: Recognize safe database session management

   This ensures that each request has its own session, preventing conflicts and resource leaks.

3. Final Answer:

   To create and close a database session for each request safely -> Option A

4. Quick Check:

   Database session management = create and close session [OK]

Hint: Remember: get_db opens and closes sessions per request [OK]

Common Mistakes:

• Thinking get_db stores data permanently
• Confusing get_db with HTTP request handling
• Assuming get_db generates HTML

2. Which of the following is the correct way to declare a dependency for a database session in a FastAPI route using Depends?

easy

A. def read_items(db = Depends(Session)):

B. def read_items(db: get_db = Session()):

C. def read_items(db: Session = get_db()):

D. def read_items(db: Session = Depends(get_db)):

Solution

1. Step 1: Understand FastAPI dependency injection syntax

   FastAPI uses Depends to inject dependencies like database sessions into route functions.

2. Step 2: Correct syntax for session injection

   The correct syntax is to type hint the parameter as Session and assign it Depends(get_db) to call the dependency function.

3. Final Answer:

   def read_items(db: Session = Depends(get_db)): -> Option D

4. Quick Check:

   Dependency injection = parameter: Type = Depends(function) [OK]

Hint: Use parameter: Type = Depends(function) for dependencies [OK]

Common Mistakes:

• Calling get_db() directly in parameter default
• Using Depends with a class instead of a function
• Swapping parameter and default values

3. Given this FastAPI route code snippet, what will be the output if the database session is correctly managed?

from fastapi import FastAPI, Depends
from sqlalchemy.orm import Session

app = FastAPI()

def get_db():
    db = Session()
    try:
        yield db
    finally:
        db.close()

@app.get('/items')
def read_items(db: Session = Depends(get_db)):
    items = db.query(Item).all()
    return items

medium

A. An error because the session is not closed

B. An empty list because the query is missing

C. A list of all items from the database

D. A syntax error due to wrong yield usage

Solution

1. Step 1: Analyze the get_db function behavior

   The get_db function creates a session, yields it for use, then closes it safely after the request.

2. Step 2: Understand the route's database query

   The route uses the session to query all Item records and returns them as a list.

3. Final Answer:

   A list of all items from the database -> Option C

4. Quick Check:

   Yielded session + query = list of items [OK]

Hint: Yielded session allows safe query and close after use [OK]

Common Mistakes:

• Assuming session is not closed causing error
• Thinking yield causes syntax error
• Believing query returns empty without data

4. Identify the error in this FastAPI database session management code:

def get_db():
    db = Session()
    yield db
    db.close()

@app.post('/add')
def add_item(item: Item, db: Session = Depends(get_db)):
    db.add(item)
    db.commit()

medium

A. The item parameter should be inside get_db

B. The session is closed after yield, so it may not close if an exception occurs

C. The Depends is used incorrectly in the route

D. The db.commit() is missing

Solution

1. Step 1: Review session closing in get_db

   The db.close() is called after yield without a try-finally block, so if an exception happens, the session may never close.

2. Step 2: Understand proper session cleanup

   Using try-finally ensures the session closes even if errors occur during request handling.

3. Final Answer:

   The session is closed after yield, so it may not close if an exception occurs -> Option B

4. Quick Check:

   Session close needs try-finally for safety [OK]

Hint: Always use try-finally to close sessions safely [OK]

Common Mistakes:

• Ignoring try-finally for session cleanup
• Forgetting to commit changes
• Misplacing Depends usage

5. You want to ensure that your FastAPI app's database sessions are properly managed and that any changes are committed only if no exceptions occur. Which of the following get_db implementations best achieves this?

hard

A. def get_db():
db = Session()
try:
yield db
db.commit()
except:
db.rollback()
raise
finally:
db.close()

B. def get_db():
db = Session()
yield db
db.commit()
db.close()

C. def get_db():
db = Session()
try:
yield db
finally:
db.close()

D. def get_db():
db = Session()
yield db
db.rollback()
db.close()

Solution

1. Step 1: Understand transaction management needs

   We want to commit changes only if no errors occur, otherwise rollback to avoid partial changes.

2. Step 2: Analyze each get_db implementation

   def get_db(): db = Session() try: yield db db.commit() except: db.rollback() raise finally: db.close() uses try-except-finally to commit on success, rollback on error, and always close the session, which is the safest approach.

3. Final Answer:

   def get_db(): db = Session() try: yield db db.commit() except: db.rollback() raise finally: db.close() -> Option A

4. Quick Check:

   Commit on success, rollback on error, always close [OK]

Hint: Use try-except-finally to commit, rollback, and close sessions [OK]

Common Mistakes:

• Committing after yield without error handling
• Not rolling back on exceptions
• Closing session without try-finally