I’m currently writing an article about the async features of the upcoming Django 3.1 release. And since I’m not an expert on this topic, I’d like to have some feedback from other people (you)
. There are probably many things I got wrong or didn’t explain very well which could be improved.
Thanks in advance, here’s the draft:
This file has been truncated.
# Django 3.1 Async
With [version 3.1](https://docs.djangoproject.com/en/3.1/topics/async/), you can
finally use asynchronous views, middlewares and tests in Django. Support for
async database queries will follow later. You don't have to change anything if
you don't want to use those new async features. All of your existing synchronous
code will run without modification in Django 3.1.
Async support for Django is on it's way for quite some time now. Since
there's support for [ASGI](https://asgi.readthedocs.io/en/latest/) included. But
there was not much benefit for end users though. The only thing you could do
concurrently were file uploads, since uploads don't reach the view layer which
was not async capable in Django 3.0.
When do you might want to use those new features? If you are building
applications that have to deal with a high number of tasks simultaneously. Here
are some examples:
* Chat services like [Slack](https://slack.com)
After Django 3.1 release, I