The Django Digestive System: A request journey in a Django app instance.

🇫🇷 La version française est disponible sur Hashnode : Le Système Digestif de Django : anatomie d'une requête HTTP vers Django Before we start, let review a few words we'll keep using Socket: ([Ref 1]) A socket is an endpoint for communication between two machines over a network. A king of pipe through which data flows. When a browser sends a request, it opens a socket connection to our server. When the server responds, it writes bytes back through that same socket. TCP, HTTP: ([Ref 2]) TCP (Transmission Control Protocol) is the transport layer. It defines standards for handling reliable delivery of data between machines. HTTP runs on top of TCP. HTTP is just text, formatted in a specific way. A browser sends an HTTP message through a TCP connection to our server. WSGI (Web Server Gateway Interface): ([Ref 3]) WSGI is the standard interface between a Python web application and a web server. A WSGI server ( Gunicorn, uWSGI ect ) sits between the internet and Django in our case: it acce