Ever wondered how your Flask or Django app actually gets from a browser click to Python code and back? Ever have trouble deciding between Gunicorn, uWSGI, Waitress, or mod_wsgi—or what Nginx/Apache is even doing there? In this presentation, **Adam Englander**—a maintainer of **Werkzeug**, the WSGI abstraction layer behind Flask—walks through the journey from CGI to WSGI, the WSGI calling convention, and the request/response lifecycle, then shows where frameworks plug in. You’ll come away with clear mental models, practical server trade-offs, deployment and scaling tips, and a quick sense of how WSGI compares to ASGI—so you can choose wisely and debug with confidence.

#VegasTech