## Asynchronous ORM interface

https://docs.djangoproject.com/en/4.1/releases/4.1/#asynchro... :

`QuerySet` now provides an asynchronous interface for all data access operations. These are named as-per the existing synchronous operations but with an `a` prefix, for example `acreate()`, `aget()`, and so on.

> The new interface allows you to write asynchronous code without needing to wrap ORM operations in `sync_to_async()`:

  async for author in Author.objects.filter(name__startswith="A"):
      book = await author.books.afirst()

> Note that, at this stage, the underlying database operations remain synchronous, with contributions ongoing to push asynchronous support down into the SQL compiler, and integrate asynchronous database drivers. The new asynchronous queryset interface currently encapsulates the necessary sync_to_async() operations for you, and will allow your code to take advantage of developments in the ORM’s asynchronous support as it evolves. […] See Asynchronous queries for details and limitations.

## Asynchronous handlers for class-based views

> View subclasses may now define async HTTP method handlers:

  import asyncio
  from django.http import HttpResponse
  from django.views import View

  class AsyncView(View):
      async def get(self, request, *args, **kwargs):
          # Perform view logic using await.
          await asyncio.sleep(1)
          return HttpResponse("Hello async world!")