Reinventing Django for the Real-Time Web
summary
Reworks Django so it can handle WebSockets, emails and IM with the same request/response guarantees by introducing Django Channels and an ASGI message layer, using a Redis or IPC channel layer and the Twisted/Autobahn based Daphne server to terminate sockets. Applications become consumers that use named channels and groups for broadcasts, workers run synchronous Django code, frontends handle thousands of idle connections on one core, load tests match Gunicorn and production users report it working.
AI-written summary · about
chapters (6)
related talks
45mWebSockets: Intro to Messaging
22mDjango Channels Teaching a mature framework new tricks
27mTaking Django Async
12mHacking Django Channels for Fun (and Profit)
38mButter smooth, interactive applications with Django...
55mWorkshop 1 - Let's Make a Realtime Game with Django Channels
40mTaking Django Async
26mUsing Django 4.2's StreamingHttpResponse and HTMX SSE to provide real time notifications