Async code does not improve the performance of CPU-bound tasks.
The number of people I've had to explain this to when advocating switching from Flask/Django -> FastAPI on a CPU-bound problem because it's "faster"... drives me nuts.
I would say the biggest issue with async Django is that if you have an existing Django site, rewriting it to use django-ninja is not that straightforward if you're heavily invested in DRF, which just hasn't moved to add async support.
Yea - 100% agree. Migrating old projects is really hard. DRF paradigms is just too opinionated and it will be basically a rebuild.
What we did for a client was to do api/v2 - and essentially do one endpoint migration at a time. api-v2 was basically its own independent application within the Django monolith.
Comments
The number of people I've had to explain this to when advocating switching from Flask/Django -> FastAPI on a CPU-bound problem because it's "faster"... drives me nuts.
I would say the biggest issue with async Django is that if you have an existing Django site, rewriting it to use django-ninja is not that straightforward if you're heavily invested in DRF, which just hasn't moved to add async support.
Yea - 100% agree. Migrating old projects is really hard. DRF paradigms is just too opinionated and it will be basically a rebuild.
What we did for a client was to do api/v2 - and essentially do one endpoint migration at a time. api-v2 was basically its own independent application within the Django monolith.