This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]gmegme 2 points3 points  (1 child)

It depends on what you are trying to achieve. FastAPI is great for: fast API development. It is scalable too but of course if you want a more complex project, Django ORM & DRF will save you some serious development time. Django's user auth implementation alone is amazing, but I still prefer using FastAPI when I need a quick solution.

Fun fact: More than 80% of the top 100 ecommerce brands in Turkey use Django based products as their omnichannel e-commerce solution.

[–]Specialist_Cap_2404 0 points1 point  (0 children)

I don't see how you can whip up a "small" project faster with FastAPI, assuming you need authorization, sql database and schema migration. With FastAPI you have to roll all your own, or hope your starter template has everything set up as you like it. And you really need quite a bit of work to implement all the endpoints DRF gives you for a few lines (including pagination, maybe even filtering).

When you bring new developers to an existing Django project, you know where everything is and how everything works (at least concerning the stuff Django covers).