Dependencies with parameters in FastAPI - Performance & Optimization

Performance: Dependencies with parameters

MEDIUM IMPACT

This affects server response time and resource usage during request handling.

Using dependencies with parameters in FastAPI endpoints

FastAPI

from fastapi import Depends, FastAPI

app = FastAPI()

def get_db_connection(param: str):
    # Simulate expensive setup
    return f"DB connection with {param}"

def get_param():
    return "my_param"

@app.get("/items/")
async def read_items(db=Depends(lambda: get_db_connection(get_param()))):
    return {"db": db}

Explicitly passing parameters ensures the dependency is called with correct arguments and can be cached or reused if designed properly.

📈 Performance GainReduces unnecessary calls and improves response time by controlling parameter passing.

Using dependencies with parameters in FastAPI endpoints

FastAPI

from fastapi import Depends, FastAPI

app = FastAPI()

def get_db_connection(param: str):
    # Simulate expensive setup
    return f"DB connection with {param}"

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

The dependency function expects a parameter but is used without passing it explicitly, causing FastAPI to call it without parameters or with default values, leading to unexpected behavior or repeated expensive calls.

📉 Performance CostTriggers repeated expensive calls per request, increasing response time.

Performance Comparison

Pattern	Dependency Calls	Parameter Passing	Response Time Impact	Verdict
Implicit parameter dependency	Multiple per request	No explicit passing	High due to repeated calls	[X] Bad
Explicit parameter passing with caching	Single or cached call	Explicit and controlled	Low, efficient reuse	[OK] Good

Rendering Pipeline

FastAPI resolves dependencies before executing the endpoint function. Dependencies with parameters require evaluating those parameters first, which can add CPU time and delay response generation.

→Dependency Resolution

→Request Handling

⚠️ BottleneckDependency Resolution stage when parameters cause repeated or expensive calls

Optimization Tips

1Always pass parameters explicitly to dependencies to avoid repeated calls.

2Cache expensive dependency results when parameters do not change.

3Profile dependency resolution time to identify bottlenecks.

Performance Quiz - 3 Questions

What is a main performance risk when using dependencies with parameters in FastAPI?

A Repeated expensive calls if parameters are not passed explicitly

B Increased bundle size due to dependencies

C Slower CSS rendering in the browser

D Higher memory usage in the client browser

DevTools: Network and Performance panels

How to check: Use the Network panel to measure response times for endpoints using dependencies with parameters. Use the Performance panel to profile CPU time spent in dependency resolution.

What to look for: Look for longer response times or CPU spikes during dependency calls indicating inefficient parameter handling.

Practice

1. What is the main purpose of using dependencies with parameters in FastAPI?

easy

A. To automatically generate HTML templates

B. To create global variables accessible everywhere

C. To replace route functions with classes

D. To customize shared code by passing arguments to dependencies

Solution

1. Step 1: Understand dependency role

   Dependencies in FastAPI are reusable pieces of code that can be shared across routes.

2. Step 2: Recognize parameter use

   Adding parameters to dependencies allows customizing their behavior for different routes or situations.

3. Final Answer:

   To customize shared code by passing arguments to dependencies -> Option D

4. Quick Check:

   Dependencies with parameters = customize shared code [OK]

Hint: Dependencies with parameters customize shared logic easily [OK]

Common Mistakes:

• Thinking dependencies create global variables
• Confusing dependencies with route handlers
• Assuming dependencies generate HTML

2. Which of the following is the correct way to pass a parameter to a dependency in FastAPI?

easy

A. Depends(get_user(user_id=5))

B. Depends(get_user, user_id=5)

C. Depends(get_user)(user_id=5)

D. Depends(get_user)[user_id=5]

Solution

1. Step 1: Recall Depends usage

   Depends expects a callable or a call to a callable that returns a dependency.

2. Step 2: Passing parameters

   To pass parameters, you call the dependency function inside Depends, like Depends(get_user(user_id=5)).

3. Final Answer:

   Depends(get_user(user_id=5)) -> Option A

4. Quick Check:

   Call dependency inside Depends to pass parameters [OK]

Hint: Call dependency inside Depends() to pass parameters [OK]

Common Mistakes:

• Passing parameters directly to Depends without calling
• Using brackets [] instead of parentheses ()
• Trying to call Depends as a function with parameters

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

from fastapi import FastAPI, Depends

app = FastAPI()

def get_multiplier(factor: int):
    def multiplier(value: int):
        return value * factor
    return multiplier

@app.get("/multiply")
async def multiply(value: int, multiply_func = Depends(get_multiplier(3))):
    return {"result": multiply_func(value)}

medium

A. Error because Depends cannot take parameters

B. {"result": 6} when value=3

C. {"result": 9} when value=3

D. {"result": 3} when value=3

Solution

1. Step 1: Understand get_multiplier

   get_multiplier(3) returns a function that multiplies input by 3.

2. Step 2: Analyze endpoint call

   When calling /multiply with value=3, multiply_func(3) returns 3 * 3 = 9.

3. Final Answer:

   {"result": 9} when value=3 -> Option C

4. Quick Check:

   Dependency returns multiplier with factor 3, output 9 [OK]

Hint: Multiply value by factor passed in dependency [OK]

Common Mistakes:

• Assuming Depends cannot take parameters
• Confusing returned function with direct value
• Mixing up multiplication factor

4. Identify the error in this FastAPI dependency usage:

def get_limit(limit: int = 10):
    return limit

@app.get("/items")
async def read_items(limit = Depends(get_limit(limit=20))):
    return {"limit": limit}

medium

A. Default value in get_limit conflicts with parameter passed

B. Cannot pass parameters directly inside Depends like get_limit(limit=20)

C. Missing type annotation for limit in read_items

D. Depends should be imported from fastapi.dependencies

Solution

1. Step 1: Check Depends usage

   Depends expects a callable or a call to a callable without parameters directly inside Depends.

2. Step 2: Correct way to pass parameters

   To pass parameters, wrap get_limit in another function or use a lambda to supply parameters.

3. Final Answer:

   Cannot pass parameters directly inside Depends like get_limit(limit=20) -> Option B

4. Quick Check:

   Depends() must wrap callable, not call with parameters directly [OK]

Hint: Wrap parameterized dependency call outside Depends() [OK]

Common Mistakes:

• Calling dependency with parameters inside Depends directly
• Ignoring need for wrapper function
• Wrong import path for Depends

5. How can you create a reusable dependency with a parameter that changes per route in FastAPI? Choose the best approach.

def common_dep(param: str):
    def dependency():
        return f"Value is {param}"
    return dependency

@app.get("/route1")
async def route1(dep = Depends(common_dep("A"))):
    return {"msg": dep}

@app.get("/route2")
async def route2(dep = Depends(common_dep("B"))):
    return {"msg": dep}

hard

A. Define a function returning a dependency function with parameter, then call it inside Depends

B. Use global variables to store param values for each route

C. Pass parameters directly to Depends without wrapping

D. Create separate dependency functions for each parameter value

Solution

1. Step 1: Understand reusable dependency pattern

   Define a function that returns a dependency function customized by parameters.

2. Step 2: Apply pattern per route

   Call this function with different parameters inside Depends for each route to customize behavior.

3. Final Answer:

   Define a function returning a dependency function with parameter, then call it inside Depends -> Option A

4. Quick Check:

   Wrap dependency with parameter function, call inside Depends [OK]

Hint: Wrap parameterized dependency in function, call inside Depends [OK]

Common Mistakes:

• Using global variables instead of parameters
• Passing parameters directly to Depends without wrapping
• Duplicating dependency functions unnecessarily