Taking Django Async
summary
Channels 2.0 is a 75% rewrite that runs on Python 3.5+ and moves from multi‑process Redis plumbing to a single process that can optionally use Redis for cross‑process pubsub, improving deploy complexity and scaling. It implements an ASGI spec for async HTTP and WebSockets, exposes bridges (sync_to_async, async_to_sync) using thread pools and event‑loop handoffs to call the synchronous ORM, and reports three servers already supporting ASGI.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:17Andrew Godwin
- 0:51History
- 6:57Django Is Not Async by Default
- 9:55Thread Pool Executor
- 11:45Event Loop
- 16:01Wsgi
- 18:08Wsgi Application
- 20:56What Does this Mean for Django
- 25:36What Is Django
related talks
40mTaking Django Async
31mReinventing Django for the Real-Time Web
29mTaking Channels Async
21mIs Django async yet?
01h 10mJust Add Await: Retrofitting Async Into Django
32mAsynchronous Django: Unlocking the Power of Async Programming
45mJust Add Await: Retrofitting Async Into Django
26mDjango 5.0: Elevating Experiences with Server-Sent Events – A Journey from Polling to Real-Time Vibe