How do async Django views interact with the ORM?
PICTURE THIS: JAVASCRIPT EVENT LOOP
Simple meaning
Default ORM calls are blocking and must not run on the event loop.
WHY — asyncio instead of guessing?
Why interviewers care about asyncio:
question about asyncio.
trade-offs, and what you would actually do on a Python project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Default ORM calls are
blocking and must not run on the event loop.
- 2Use the async ORM
(aget, afilter) in supported Django versions, or wrap sync ORM in sync_to_async with thread_sensitive=True so the same connection is not shared unsafely.
- 3Mixing one connection across
threads is undefined behavior.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Default ORM calls are blocking and must not run on the event loop. Use the async ORM (aget, afilter) in supported Django versions, or wrap sync ORM in sync_to_async with thread_sensitive=True so the same connection is not shared unsafely.