This has an explanation of the motivation for this project:<p><a href="https://django-ninja.rest-framework.com/motivation/" rel="nofollow">https://django-ninja.rest-framework.com/motivation/</a><p>It sounds super interesting, it fits the middle ground between Django Rest Framework and FastAPI taking the best of both. Full support for Django and particularly it’s ORM (hard to do with FastAPI as the Django ORM is not yet async and can’t be used with FastAPI)<p>I like that it supports both sync and async as I’m personally not convinced about the use of async Python everywhere. I could see this being brilliant for an api where the majority is simple sync code but with a few endpoint with long running responses or where you need multiple concurrent requests to DBS or other APIs.<p>(Edited for clarity, thanks vladvasiliu)
> FAST execution: Very high performance thanks to Pydantic and async support.<p>> Benchmark: 750 requests per second.<p>Think we're gonna need a couple of zeroes on that number to throw around words like "very high performance".
The approach for this I have taken lately is this:<p>1. A custom made serializer. This is the most complicated 150 lines of code in that it can traverse Django ORM objects/query sets and output them to JSON. It supports explicit included and excluded fields and included relationships which it automatically prefetches.<p>2. Custom middleware that parses any application/json request bodies in <i>request.data</i>.<p>3. I use Django forms on any data going from client to server for validation. Works great, no reason to make this complicated.<p>That’s it. Now I can have a REST API written as normal Django views. It is significantly more performant Thant DRF since it doesn’t need to check for a whole lot of different complicated field types when serializing. It’s easy to understand (just call <i>serialize(users, excluded_fields=[“password”], relationships=[“books.chapters”])</i> to return JSON to the client; you can also annotate your models to include/exclude fields and relationships by default). It has validation errors built in via Django forms. It just works.
This project is very clever, because as a Django developer, when I tried to use. FastAPI, I didn't get the faith to learn another ORM.<p>I've been using django ninja for months and I can say that it's a very good replacement to DRF. It's way simpler to use and less bloated, thanks to pydantic.<p>However I would not use it for important projects in production, because of a lack of support and documentation, and the fact that it relies almost entirely on a single developer (like many other projects, right).
When I read the tutorial and run on uvicorn with my lack of experience in Python language, it's significantly slow (3,000+ rps using this framework manage.py vs <500 rps on uvicorn)?