django-async-orm VS django-ninja

I'm not sure if its official. Would love some more guidance/clarity/docs/funding from the django foundation on what it looks like to migrate legacy code to the new ways.

The rednaks repo works great for just giving the new async stuff a go. If everything else is also using async.

I did some experimentation with this. And its a pain trying to migrate a production application that uses gevent and psycogreen2.

The documentation on the code migration path is pretty sparse.

The main hiccup that I ran into was psycogreen2 not being supported.

https://stackoverflow.com/questions/67735453/django-async-or...

https://github.com/rednaks/django-async-orm/discussions/9

> 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

Django Ninja

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.

A good compromise I have found is to use Django Ninja [1]. It is inspired by FastAPI, so it has a lot of the nice things like the automatically generated Swagger/OpenAPI docs, as well as having routers as decorators, and using python types for automatic serialization.

While I think FastAPI is great in its first class async support, Django has the Django ORM, plus Django Admin, which for me have been indisposable.

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

I honestly just followed the tutorial on https://django-ninja.rest-framework.com/ because I read about it and wanted to test it out / learn something new.

I find https://django-ninja.rest-framework.com/ even more awesome these days because it natively integrates with Django ORM, which I prefer over alternatives such as SQLAlchemy.

If you've used FastAPI before, you should check out django-ninja for your views and just familiarize yourself with the Django ORM to do database operations (e.g. https://docs.djangoproject.com/en/4.1/topics/db/queries/). That'll probably get you 80% of what you need.