-
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
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
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
-
benchmark-django-fastapi
Some rough benchmarks of django with various configurations for WSGI / ASGI, fastapi, uvicorn
https://github.com/rednaks/django-async-orm/discussions/6
Everything works great if everything is already using the regular threading and asyncio/async methods, or JUST gevent/psycogreen.
The django documentation suggests mounting WSGI into ASGI.
But, it breaks down immediately going between the two paradigms.
I put a little experiment together a bit ago to see what would work in production, and my results.
https://github.com/allen-munsch/benchmark-django-fastapi
