tortoise-orm VS django-ninja

To do this, we can use the Tortoise-ORM. Begin by installing the package:

If I was answering this question but for python, I'd recommend something like prefect, boto3, or tortoise-orm -- not extremely complex and with a pretty comprehensible featureset.

If you're just starting with relational databases i suggest you use an ORM an object relational mapper. Which allows you to use simple python to make all database interactions. And i recommend using tortoise ORM.

Does anybody have any experience with that? Can I use Django in my asyncio application without *actually using Django? Or should sth like Tortoise ORM be preferred?

Tortoise ORM looks a lot like the django ORM https://tortoise.github.io

Thanks, it's great to see Django adding slowly but surely in all sorts of places.

By the way, have you looked at tortoise orm, which is a fully async python ORM with very Django-like syntax? [1]

[1] https://github.com/tortoise/tortoise-orm

Django Ninja [1], it forever changed how I write Django project, in a way so elegant and productive.

[1]: https://django-ninja.dev/

Django Ninja is a RESTful wrapper for Django, while UtilMeta Python Framework uses a more concise declarative ORM Schema for Django and other future-supporting ORMs like sqlachemy and Peewee to build RESTful APIs more efficiently, and supports not only Django but all Python mainstream frameworks like Django, Flask, Starlette, FastAPI, Sanic, Tornado, etc.

I can't recommend [django-ninja](https://github.com/vitalik/django-ninja) enough. It's an easy to use, extremely fast, typed API for django. I've found it to be better in almost all aspects when compared to djangorestframework.

It's gaining popularity but is still widely unknown.

> The only place I really see Django at large companies is as an api using DRF or something.

This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1].

Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything.

There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them.

[1] https://django-ninja.rest-framework.com/

[2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admi...

Personally, I also prefer django-ninja to DRF.

Actually that's not fully true. If you mix async and sync codes in django-ninja there will be some errors. Where's the proof ? django-ninja doesn't support async auth

Subscribe to this issue :D

Also recommend Django-Ninja. It basically reimplements fastapi's type and decorator-based API construction, but embedded directly in django so you have access to django's ORM and middleware library.