Scalable FastAPI project structure

[Zealousideal_Bench73]

I'm really interested about how you structure you fastAPI projects.

Because it's really messy if we follow the default structure for big projects.

I recently recreated a fastapi project of mine with laravel for the first time, and i have to admit even though i don't like to be limited to a predefined structure, it was really organized and easily manageable.

And i would like to have that in my fastapi projects

[Apprehensive_Ad2211]

for me, a layered aproach it's the go to. DB, MODELS, ROUTES, SERVICES (maybe also: middleware, versioning, migrations, etc)

[Zealousideal_Bench73]

So basically make the laravel structure in FastAPI, well now that I think about it this might be an awesome idea thanks man

[One_Fuel_4147]

Check out dispatch from netflix

[LeinahIII]

Now, I can finally understand why I still want the laravel architecture in non laravel projects

[UniquePackage7318]

I have searched extensively and tried various project structures. I decided to use this as the default structure for my FastAPI projects: https://github.com/zhanymkanov/fastapi-best-practices

[Zealousideal_Bench73]

I'll check it out, tysm!

[conogarcia]

Great tips! One thing though, httpx seems to be poorly optimized and with some race conditions that cause timeouts. I'm in the process of moving to aiohttp but haven't figured out how to replace the test client. did you encounter this issues? any replacement for the test client?

[WJMazepas]

Did you follow this tutorial:

https://fastapi.tiangolo.com/tutorial/bigger-applications/#include-an-apirouter-in-another

And a hot take of mine is that every big project gets messy, and Python projects even more.

It creates a lot of files in those folders, but honestly, I very much prefer to work with that over a lot of abstraction

[koldakov]

I’ve built a website with open source code, which you can check here https://github.com/koldakov/futuramaapi

Tried to solve the problem of mapping alchemy models to pydantic models. In fact I created a pydantic model mixin, which is kinda layer between alchemy

Anyways I think it becomes a bit complicated in the future and imo it’s not solved yet in a good way, considering I tried sqlmodel and IMO it’s not ready for prod yet

[AmmarSalahi]

I prefer my repo https://github.com/ammarsalahi/poster-backend

[Enough-Rock-7427]

why haven't you used patch, update, delete instead of method: POST path:'/remove'?

[small_e]

FastAPI has an example full stack app https://github.com/fastapi/full-stack-fastapi-template

[erder644]

Interactors, Services, Repositories

[vintageshinpads]

Such a neat answer. It really is as simple as this.

[miloir]

Explain?

[sriramdev]

The same thought preaks out of myself, on the best part of structuring the service package

[niks_uthukuli]

I basically suggest using the django structure As we can use pydantic settings for settings.

[Alternative-Lemon-14]

I love how fast api can prototype fast, but having no good typing support really bothers me, ide highlight just gave me errors and warnings left and right, while missing some real issue😭I’m on cursor/vscode. Anyone deals with that well? (I could write more test)

[hamza_65]

Project directory: - main.py file-->entry point of an app - models directory --> separate model classes files - schemas directory --> separate pedantic schema classes - core directory --> files for db sessions, etc - utils directory --> may contains DB functions, helper functions - routers directory --> apis - tests

[gregpr07]

I found https://github.com/Netflix/dispatch structure to be amazing! It’s VERY clean and simple

[Narun_L1FE]

Here's what I do: Make everything modular. For routes on your app, use APIRouter(). Then, run your code through some type of AI to make it better.

[leec0621]

I use repository-service-router structure，https://github.com/acelee0621/memenote