Gunicorn for production serving in Flask - Step-by-Step Execution

Concept Flow - Gunicorn for production serving

Write Flask app

↓

Install Gunicorn

↓

Run Gunicorn with app

↓

Gunicorn starts workers

↓

Workers listen for requests

↓

Requests received -> handled by workers

↓

Responses sent back to clients

↓

Monitor and restart workers if needed

This flow shows how you write a Flask app, then use Gunicorn to run it in production by starting worker processes that handle incoming requests and send responses.

Execution Sample

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    return 'Hello, World!'

# Run with: gunicorn app:app

A simple Flask app that returns 'Hello, World!' at the home page, served by Gunicorn workers in production.

Execution Table

Step	Action	Gunicorn Process	Worker Process	Result
1	Start Gunicorn with 'gunicorn app:app'	Master process starts	No workers yet	Gunicorn master ready
2	Gunicorn spawns worker processes	Master manages workers	Workers start and load Flask app	Workers ready to accept requests
3	Client sends HTTP request	Master routes request	Worker receives request	Worker begins processing
4	Worker calls Flask app route function	Master waits	Flask app returns 'Hello, World!'	Response generated
5	Worker sends HTTP response	Master waits	Response sent to client	Client receives 'Hello, World!'
6	Worker waits for next request	Master monitors workers	Idle, ready for next request	System stable
7	If worker crashes	Master detects failure	Worker restarts	Service continues without downtime

💡 Gunicorn master and workers run continuously to serve requests until stopped.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Master Process	Not running	Running, managing workers	Running	Running	Running	Running
Worker Processes	None	Started, loaded app	Received request	Processed request	Sent response	Idle, waiting
Request	None	None	Received by worker	Being processed	Response sent	None
Response	None	None	None	Generated	Sent to client	None

Key Moments - 3 Insights

Why does Gunicorn start multiple worker processes instead of just one?

Gunicorn starts multiple workers to handle many requests at the same time, improving performance and reliability. See execution_table step 2 where workers start and load the app.

What happens if a worker process crashes during request handling?

The master process detects the crash and restarts the worker automatically, so the service keeps running without downtime. This is shown in execution_table step 7.

Why don't we run the Flask app directly in production?

Flask's built-in server is for development only and can't handle many users or restart workers. Gunicorn manages multiple workers and is designed for production, as shown in the concept flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of worker processes after step 2?

A Workers are idle and waiting for requests

B Workers have crashed

C Workers are started and have loaded the Flask app

D Workers have sent responses to clients

💡 Hint

Check the 'Worker Process' column in execution_table at step 2

At which step does the worker process send the HTTP response back to the client?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Look for 'Response sent to client' in the 'Result' column of execution_table

If the master process stops managing workers, what will happen according to the flow?

A Workers will continue handling requests normally

B Workers will crash and not restart

C Workers will become master processes

D Nothing changes, system runs as usual

💡 Hint

Refer to execution_table step 7 about master detecting worker failure and restarting

Concept Snapshot

Gunicorn runs Flask apps in production by starting a master process and multiple worker processes.
Workers handle incoming HTTP requests concurrently.
Master monitors workers and restarts them if they crash.
Run with: gunicorn app:app
This setup improves performance and reliability over Flask's built-in server.

Full Transcript

This visual execution shows how Gunicorn serves a Flask app in production. First, you write a Flask app with routes. Then you install Gunicorn and run it with your app. Gunicorn starts a master process that manages several worker processes. Each worker loads the Flask app and listens for HTTP requests. When a client sends a request, the master routes it to a worker. The worker calls the Flask route function, generates a response, and sends it back to the client. Workers stay ready for new requests. If a worker crashes, the master detects this and restarts it automatically. This setup allows your Flask app to handle many users reliably and efficiently in production.