From WSGI to ASGI - Django 3.0
summary
Built a small web app from scratch to trace how requests flow, discovering WSGI’s callable environ, start_response and ASGI’s coroutine application(scope, receive, send). Shows that Django 3.0 ships ASGI so Django can handle websockets, streaming (more_body chunks) and nonblocking IO, while WSGI blocks a worker on long IO. Mentions Gunicorn/uWSGI for WSGI and Uvicorn/Hypercorn/Daphne for ASGI, notes ASGI raises concurrent throughput for IO-bound cases but WSGI can still outperform in some sync-heavy workloads.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:14Background
- 1:32Memes
- 2:23Exceptions
- 3:48Whiskey
- 4:29What is an interface
- 9:05ASGI
- 12:11Scope
- 12:35Socket Communication
- 13:42ASCII Communication
- 14:21ASGI Servers
- 14:44Questions
- 16:10Channels
related talks
26mInside web framework: intro to the ASGI spec, middleware and apps
31mInside ASGI The Engine Behind Modern Python Web Frameworks
31mHey, Python-Web-Community! What's going on?
24mA Brief History of Python Web Frameworks
26mUsing Django as a Micro-Framework: Hacking on the HTTP handlers..
55mKeynote: The Natural State of Computers
47mASGI in depth
23mµDjango, an Asynchronous Microservices Technique with Practical Examples