Async vs sync decision in FastAPI

Introduction

Choosing between async and sync helps your FastAPI app handle tasks efficiently. Async lets your app do many things at once, while sync does one thing at a time.

When your app needs to handle many users at the same time without waiting.

When your code calls slow operations like database queries or web requests.

When you want simple code that runs step-by-step without extra complexity.

When you have CPU-heavy tasks that don't benefit from async.

When integrating with libraries that only support synchronous calls.

Syntax

FastAPI

async def function_name():
    # async code here

def function_name():
    # sync code here

Use async def to define asynchronous functions.

Use regular def for synchronous functions.

Examples

This is a synchronous route handler. It runs step-by-step.

FastAPI

from fastapi import FastAPI

app = FastAPI()

@app.get("/sync")
def read_sync():
    return {"message": "This is sync"}

This is an asynchronous route handler. It can pause and let other tasks run during await.

FastAPI

from fastapi import FastAPI
import asyncio

app = FastAPI()

@app.get("/async")
async def read_async():
    await asyncio.sleep(1)
    return {"message": "This is async"}

Sample Program

This FastAPI app has two endpoints. The /sync endpoint blocks for 1 second, stopping other tasks. The /async endpoint waits 1 second without blocking, letting other tasks run.

FastAPI

from fastapi import FastAPI
import asyncio

app = FastAPI()

@app.get("/sync")
def sync_endpoint():
    # Simulate a blocking task
    import time
    time.sleep(1)
    return {"message": "Finished sync task"}

@app.get("/async")
async def async_endpoint():
    # Simulate a non-blocking task
    await asyncio.sleep(1)
    return {"message": "Finished async task"}

Important Notes

Async is great for waiting on slow tasks like network calls.

Sync is simpler and good for quick or CPU-heavy tasks.

Mixing async and sync incorrectly can cause problems; keep your code consistent.

Summary

Async lets your app handle many things at once by waiting without blocking.

Sync runs tasks one after another and can block other work.

Choose async for I/O-bound tasks and sync for CPU-bound or simple tasks.

Practice

1. In FastAPI, when should you choose an async function over a def synchronous function?

easy

A. When the task is CPU-heavy and requires intense calculations

B. When the task involves waiting for external resources like databases or APIs

C. When you want the function to run slower

D. When you want to block other tasks until this finishes

Solution

1. Step 1: Understand async purpose in FastAPI

   Async functions let your app wait for external tasks like database calls without stopping other work.

2. Step 2: Match task type to function type

   Waiting for external resources is I/O-bound, so async is best to avoid blocking.

3. Final Answer:

   When the task involves waiting for external resources like databases or APIs -> Option B

4. Quick Check:

   Async = I/O-bound tasks [OK]

Hint: Use async for waiting tasks, sync for CPU tasks [OK]

Common Mistakes:

• Choosing async for CPU-heavy tasks
• Thinking async makes code slower
• Using sync for I/O-bound tasks

2. Which of the following is the correct way to define an asynchronous route handler in FastAPI?

easy

A. async get_data def(): return {'msg': 'Hello'}

B. def async get_data(): return {'msg': 'Hello'}

C. def get_data() async: return {'msg': 'Hello'}

D. async def get_data(): return {'msg': 'Hello'}

Solution

1. Step 1: Recall Python async function syntax

   Async functions start with async def followed by the function name and parentheses.

2. Step 2: Check each option's syntax

   Only async def get_data(): return {'msg': 'Hello'} uses the correct async def syntax; others are invalid Python syntax.

3. Final Answer:

   async def get_data(): return {'msg': 'Hello'} -> Option D

4. Quick Check:

   Async function syntax = async def [OK]

Hint: Async functions start with 'async def' in Python [OK]

Common Mistakes:

• Placing async keyword after def
• Using 'def async' instead of 'async def'
• Incorrect order of keywords

3. Consider this FastAPI code snippet:

from fastapi import FastAPI
import time

app = FastAPI()

@app.get('/sync')
def sync_endpoint():
    time.sleep(2)
    return {'message': 'Done'}

@app.get('/async')
async def async_endpoint():
    await some_async_task()
    return {'message': 'Done'}

What is the main difference in behavior between /sync and /async endpoints?

medium

A. Both block other requests equally

B. /async blocks other requests; /sync allows concurrency

C. /sync blocks other requests during sleep; /async allows concurrent handling

D. Both allow full concurrency without blocking

Solution

1. Step 1: Understand sync endpoint behavior

   The sync_endpoint uses time.sleep(2), which blocks the thread and stops handling other requests during that time.

2. Step 2: Understand async endpoint behavior

   The async_endpoint uses await on an async task, allowing the server to handle other requests while waiting.

3. Final Answer:

   /sync blocks other requests during sleep; /async allows concurrent handling -> Option C

4. Quick Check:

   Sync blocks, async allows concurrency [OK]

Hint: Sync blocks during wait; async frees server to handle others [OK]

Common Mistakes:

• Assuming sync allows concurrency
• Thinking async blocks like sync
• Confusing await with blocking

4. You wrote this FastAPI route:

@app.get('/data')
async def get_data():
    result = time.sleep(1)
    return {'result': result}

What is the problem with this code?

medium

A. Using time.sleep inside async blocks the event loop, causing delays

B. Missing await keyword before time.sleep

C. Function should not be async if it returns a dictionary

D. No problem; code works fine

Solution

1. Step 1: Identify blocking call in async function

   time.sleep(1) is a blocking call that pauses the whole thread, including the async event loop.

2. Step 2: Understand async best practices

   In async functions, use non-blocking calls like await asyncio.sleep(1) to avoid blocking the event loop.

3. Final Answer:

   Using time.sleep inside async blocks the event loop, causing delays -> Option A

4. Quick Check:

   Blocking calls in async cause delays [OK]

Hint: Never use time.sleep in async; use await asyncio.sleep instead [OK]

Common Mistakes:

• Trying to await time.sleep
• Ignoring blocking effect of time.sleep
• Thinking async auto makes code non-blocking

5. You have a FastAPI app that fetches data from a slow external API and then processes it heavily with CPU calculations. How should you design your endpoint for best performance?

hard

A. Make the endpoint async to await the API call, then run CPU work in a separate thread or process

B. Make the endpoint fully async and run CPU work directly inside it

C. Make the endpoint synchronous and run both API call and CPU work sequentially

D. Use synchronous endpoint but call the API asynchronously

Solution

1. Step 1: Separate I/O-bound and CPU-bound tasks

   Fetching data from an external API is I/O-bound and benefits from async to avoid blocking.

2. Step 2: Handle CPU-heavy work properly

   CPU-heavy processing blocks the event loop if run directly in async code, so it should run in a separate thread or process.

3. Step 3: Combine async I/O with offloaded CPU work

   Use async endpoint to await API call, then offload CPU work to thread/process to keep responsiveness.

4. Final Answer:

   Make the endpoint async to await the API call, then run CPU work in a separate thread or process -> Option A

5. Quick Check:

   Async for I/O + thread/process for CPU [OK]

Hint: Async for waiting; thread/process for CPU work [OK]

Common Mistakes:

• Running CPU work directly in async code
• Making endpoint fully sync causing blocking
• Mixing async and sync calls incorrectly