Django Ninja
github.com
Django Ninja
1–4 of 4 posts
Re: Django Ninja
#2My hunch is that it's probably better to stay with the Django way of doing things (DRF), in spite of the online chatter calling it bloated.
Re: Django Ninja
#3I'm looking into adding some sort of REST API layer to a Django app and I've been reading some negative things about Django Rest Framework (DRF), which is the default choice for this functionality in Django-world. This project is inspired by FastAPI and is potentially a lighter weight alternative to DRF and I'm wondering if HNers have experience with it and/or DRF. My hunch is that it's probably better to stay with t…
so at this moment the project is slowly growing (about 10+ companies I know are starting to adopt it )
Main benefits are - OpenAPI spec oriented - lightweigh and 0 intrusion to django-core (basically django-ninja is just a validation/documentation layer for django views) - high performance (some cases can be 2x-100x faster with than DRF)
Re: Django Ninja
#4I'm looking into adding some sort of REST API layer to a Django app and I've been reading some negative things about Django Rest Framework (DRF), which is the default choice for this functionality in Django-world. This project is inspired by FastAPI and is potentially a lighter weight alternative to DRF and I'm wondering if HNers have experience with it and/or DRF. My hunch is that it's probably better to stay with t…
Hello, I'm the author so at this moment the project is slowly growing (about 10+ companies I know are starting to adopt it ) Main benefits are - OpenAPI spec oriented - lightweigh and 0 intrusion to django-core (basically django-ninja is just a validation/documentation layer for django views) - high performance (some cases can be 2x-100x faster with than DRF)