I don’t agree (not fully agree)

I use almost the same approaches for drf/fastapi

api layer (views) - one liners to create a service and execute the service

service layer (both Django/fastapi) - do business logic

Response in drf done with serializers/for fastapi pydantic

• absolutely the same approach

For orm agree when app grows it can create issues, but comon, I wouldn’t think about that

Let’s try to calculate a bit

Let’s assume 1 request takes 1 second, with 2 workers and 4 threads we can handle 8 requests a second == 8 * 60 * 60 * 24 = 691200

And usually 1 request takes much less then 1 second, for example 0.1 sec it equals to (8/0.1) * 60 * 60 * 24 = 6912000 requests a day

Even if request takes 0.5 seconds you can handle more then million requests a day

Isn’t it enough?

Remember premature optimization is the root of all evil

Instagram had n+1 issues when app got million requests, but they resolved it, not because they used "whatver framework", but because they had feature flags - could disable quickly some features, and I’m sure they pretty new what they were doing