DRF falls apart very quickly when you get away from the "simple CRUD" use cases. The Serializer mechanism causes N+1 query behavior by default with non-trivial

DRF falls apart very quickly when you get away from the "simple CRUD" use cases. The Serializer mechanism causes N+1 query behavior by default with non-trivial models. This is exacerbated by the fact that they all run in sequence because there's no async support. It's documentation is also pretty poor, IMO. > There’s a vibe, or assumption around Ninja that it’s “newer”, or “like FastAPI”, or “the way forward”, none of which are objective benefits per se. The creator of DRF also created starlette, which underpins FastAPI. If DRF works for you cool, but that doesn't mean the community hasn't moved on.