Understanding How Nginx, WSGI, and Flask Work Together

Previously the relationship among Nginx, WSGI (or uWSGI), and Flask (or Django) was confusing; this article resolves that by presenting a three‑layer model: the web‑server layer, the WSGI layer, and the web‑framework layer.

Web‑Server Layer

The web server receives an HTTP request, processes it, and returns a response. Common servers include Nginx, Apache, and IIS. In the three‑layer diagram the web server is the first component that handles the client request.

Web‑Framework Layer

The framework simplifies building web applications and provides dynamic data for HTTP requests. Using Flask as an example, the following code creates a minimal web app:

from flask import Flask

app = Flask(__name__)

@app.route('/hello')

def hello_world():

return 'Hello World!'

if __name__ == '__main__':

app.run(host='0.0.0.0', port=8080)

Developers using the framework focus on business logic and do not need to manage low‑level request handling.

WSGI Layer

WSGI (Web Server Gateway Interface) is not a server nor an API; it is a Python‑specific interface specification that defines how a web server and a web application communicate. Any server and application that follow the WSGI protocol can be combined.

A simple WSGI application looks like this:

def application(env, start_response):

start_response('200 OK', [('Content-Type', 'text/html')])

return [b"Hello World"]

The server calls application, passing an env dictionary with request metadata and a start_response callable to set status and headers. The function returns the response body.

Related Terms

uwsgi : a protocol similar to WSGI; the uWSGI server implements this protocol.

uWSGI : a web server that supports both the uwsgi and WSGI protocols; it belongs to the web‑server layer.

CGI : a language‑agnostic gateway interface that predates WSGI; it is less efficient and rarely used in production today.

In practice, WSGI acts as a bridge connecting the web server (e.g., Nginx) with the web framework (e.g., Flask). The article concludes with a conversational illustration of how Nginx, WSGI, and Flask interact to handle a request.