Why dependency injection matters in FastAPI

Introduction

Dependency injection helps your code stay clean and easy to change. It lets you give parts of your app what they need without hard coding them inside.

When you want to share a database connection across many parts of your app.

When you need to swap one service for another without changing your main code.

When writing tests and you want to replace real parts with fake ones easily.

When you want to keep your code organized and avoid repeating setup steps.

Syntax

FastAPI

from fastapi import Depends

app = FastAPI()

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

@app.get("/items/")
async def read_items(db = Depends(get_db)):
    return db.query_items()

Depends() tells FastAPI to run the function and give its result to your endpoint.

You can use yield in dependency functions to handle setup and cleanup.

Examples

This example shows using a dependency to check a token before running the endpoint.

FastAPI

from fastapi import Depends, HTTPException

app = FastAPI()

def get_token_header():
    token = "expected-token"
    if token != "expected-token":
        raise HTTPException(status_code=400, detail="Invalid token")
    return token

@app.get("/secure-data")
async def secure_data(token: str = Depends(get_token_header)):
    return {"data": "This is secure"}

Here, a class instance is injected as a dependency to keep code clean and testable.

FastAPI

from fastapi import Depends

app = FastAPI()

class Service:
    def do_work(self):
        return "work done"

def get_service():
    return Service()

@app.get("/work")
async def work(service: Service = Depends(get_service)):
    return {"result": service.do_work()}

Sample Program

This simple FastAPI app shows how dependency injection passes a message to the endpoint without hard coding it inside.

FastAPI

from fastapi import FastAPI, Depends

app = FastAPI()

# Dependency function
async def get_message():
    return "Hello from dependency!"

# Endpoint using dependency injection
@app.get("/greet")
async def greet(message: str = Depends(get_message)):
    return {"message": message}

Important Notes

Dependencies can be reused in many endpoints to avoid repeating code.

Using dependency injection makes testing easier by allowing you to swap real parts with mocks.

FastAPI handles calling and cleaning up dependencies automatically.

Summary

Dependency injection helps keep your code clean and flexible.

It allows easy sharing and swapping of parts like services or database connections.

FastAPI makes using dependency injection simple with the Depends function.

Practice

1. Why is dependency injection important in FastAPI applications?

easy

A. It forces you to write all code inside one big function.

B. It automatically generates HTML pages for your API.

C. It speeds up the server by caching all responses.

D. It helps keep code clean and makes components easy to share or replace.

Solution

1. Step 1: Understand the purpose of dependency injection

   Dependency injection allows you to provide parts like services or database connections to your functions without hardcoding them.

2. Step 2: Recognize benefits in FastAPI

   This makes your code cleaner and more flexible, as you can easily swap or share components.

3. Final Answer:

   It helps keep code clean and makes components easy to share or replace. -> Option D

4. Quick Check:

   Dependency injection = clean, flexible code [OK]

Hint: Think: clean code and easy swapping [OK]

Common Mistakes:

• Confusing dependency injection with caching
• Thinking it generates HTML automatically
• Believing it forces monolithic code

2. Which of the following is the correct way to declare a dependency in a FastAPI path operation?

easy

A. def read_data(db = Depends(get_db)):

B. def read_data(db: Depends = get_db):

C. def read_data(db: Depends(get_db)):

D. def read_data(db = get_db()):

Solution

1. Step 1: Recall FastAPI dependency syntax

   FastAPI uses Depends() inside the function parameter default value to declare dependencies.

2. Step 2: Check each option

   def read_data(db = Depends(get_db)): correctly uses db = Depends(get_db). Others misuse type hints or call the function directly.

3. Final Answer:

   def read_data(db = Depends(get_db)): -> Option A

4. Quick Check:

   Depends() in default value = correct syntax [OK]

Hint: Use Depends() as default parameter value [OK]

Common Mistakes:

• Calling the dependency function instead of passing it
• Using Depends as a type hint incorrectly
• Assigning dependency without Depends()

3. Given this FastAPI code snippet, what will be printed when accessing the endpoint?

from fastapi import FastAPI, Depends
app = FastAPI()

def get_number():
    return 42

@app.get("/number")
def read_number(num: int = Depends(get_number)):
    print(f"Number is {num}")
    return {"number": num}

medium

A. Number is 42 printed in console, response JSON {"number": 42}

B. Number is 0 printed in console, response JSON {"number": 0}

C. Error because get_number is not awaited

D. Response JSON {"number": null} with no print

Solution

1. Step 1: Understand dependency injection behavior

   The get_number function returns 42 and is injected as the parameter num.

2. Step 2: Trace the endpoint execution

   When the endpoint is called, it prints "Number is 42" and returns JSON with number 42.

3. Final Answer:

   Number is 42 printed in console, response JSON {"number": 42} -> Option A

4. Quick Check:

   Depends injects 42, prints and returns it [OK]

Hint: Dependency returns 42, so print shows 42 [OK]

Common Mistakes:

• Thinking dependency must be async
• Expecting default 0 instead of injected value
• Confusing print output with response content

4. What is wrong with this FastAPI dependency usage?

def get_db():
    return "db_connection"

@app.get("/items")
def read_items(db = get_db()):
    return {"db": db}

medium

A. The function get_db is missing async keyword.

B. The dependency function is called immediately instead of injected.

C. The endpoint is missing a return statement.

D. Depends() is used incorrectly inside the function body.

Solution

1. Step 1: Identify how dependency should be declared

   Dependencies must be passed as Depends(get_db), not by calling get_db() directly.

2. Step 2: Explain the problem in the code

   Calling get_db() runs it once at startup, not per request, losing flexibility and benefits of injection.

3. Final Answer:

   The dependency function is called immediately instead of injected. -> Option B

4. Quick Check:

   Call vs Depends() matters for injection [OK]

Hint: Use Depends(), don't call dependency function [OK]

Common Mistakes:

• Calling dependency function instead of passing Depends()
• Confusing async requirement with dependency injection
• Ignoring missing return statement (it exists here)

5. You want to share a database connection across multiple endpoints in FastAPI using dependency injection. Which approach best ensures the connection is created once per request and properly closed after?

hard

A. Pass the connection as a query parameter to each endpoint.

B. Create the connection globally once outside any function and reuse it everywhere.

C. Use a dependency function with yield that opens the connection, yields it, then closes it after.

D. Call the connection function directly inside each endpoint without Depends.

Solution

1. Step 1: Understand lifecycle management with dependencies

   Using yield in a dependency function allows setup before yield and cleanup after the request finishes.

2. Step 2: Compare options for connection management

   Use a dependency function with yield that opens the connection, yields it, then closes it after. correctly manages connection per request lifecycle. Others either create global state or misuse parameters.

3. Final Answer:

   Use a dependency function with yield that opens the connection, yields it, then closes it after. -> Option C

4. Quick Check:

   Yield in dependency = setup and cleanup per request [OK]

Hint: Use yield in dependency for setup and cleanup [OK]

Common Mistakes:

• Using global connection risking concurrency issues
• Calling connection directly losing cleanup control
• Passing connection via query parameters insecurely