Gunicorn for production serving in Flask - Mini Project: Build & Apply

Gunicorn for Production Serving with Flask

📖 Scenario: You have created a simple Flask web application for a small online store. Now, you want to serve this app in a production environment using Gunicorn, a popular WSGI server that is more robust and efficient than Flask's built-in server.

🎯 Goal: Set up a Flask app and configure Gunicorn to serve it in production mode.

📋 What You'll Learn

Create a basic Flask app with one route

Define a variable for the number of Gunicorn worker processes

Write the command to run the Flask app with Gunicorn using the worker count

Add a configuration to bind Gunicorn to localhost on port 8000

💡 Why This Matters

🌍 Real World

Using Gunicorn to serve Flask apps is common in real-world web deployments to handle multiple requests efficiently and reliably.

💼 Career

Understanding how to configure Gunicorn is important for backend developers and DevOps engineers working with Python web applications in production.

1

Create a basic Flask app

Create a Flask app by importing Flask from flask and instantiate it as app. Define a route / that returns the string 'Hello, Gunicorn!'.

Flask

from flask import Flask

app = Flask(__name__)

# Define a route for '/' that returns 'Hello, Gunicorn!'
# Your code here

Hint

Use @app.route('/') to define the route and a function that returns the greeting string.

2

Set Gunicorn worker count

Create a variable called workers and set it to 3. This will be the number of Gunicorn worker processes to handle requests.

Flask

from flask import Flask

app = Flask(__name__)

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

# Set the number of Gunicorn workers
# Your code here

Hint

Just create a variable named workers and assign it the number 3.

3

Write Gunicorn run command

Write a string variable called gunicorn_command that contains the command to run Gunicorn with the Flask app. Use the format gunicorn -w {workers} app:app where workers is the variable from step 2.

Flask

from flask import Flask

app = Flask(__name__)

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

workers = 3

# Create the Gunicorn command string using workers
# Your code here

Hint

Use an f-string to insert the workers variable into the command string.

4

Add Gunicorn bind configuration

Add bind = '127.0.0.1:8000' as a string variable to specify Gunicorn should listen on localhost port 8000.

Flask

from flask import Flask

app = Flask(__name__)

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

workers = 3

gunicorn_command = f'gunicorn -w {workers} app:app'

# Add bind address for Gunicorn
# Your code here

Hint

Set the bind variable to the string '127.0.0.1:8000'.

Practice

1. What is the main purpose of using Gunicorn with a Flask application in production?

easy

A. To automatically generate Flask routes based on database models

B. To provide a graphical user interface for Flask applications

C. To efficiently handle multiple user requests by running the Flask app with multiple workers

D. To replace Flask's built-in development server with a simpler one

Solution

1. Step 1: Understand Flask's built-in server limitations

   Flask's built-in server is single-threaded and not suitable for handling many users in production.

2. Step 2: Role of Gunicorn in production

   Gunicorn runs multiple worker processes to handle many requests efficiently in production environments.

3. Final Answer:

   To efficiently handle multiple user requests by running the Flask app with multiple workers -> Option C

4. Quick Check:

   Gunicorn improves concurrency = A [OK]

Hint: Gunicorn runs multiple workers to handle many users [OK]

Common Mistakes:

• Thinking Gunicorn provides a GUI
• Believing Gunicorn auto-generates routes
• Assuming Gunicorn is a simpler server than Flask's

2. Which of the following is the correct command to start a Flask app named app inside a module called myapp using Gunicorn?

easy

A. gunicorn myapp:app

B. gunicorn myapp.app

C. gunicorn app.myapp

D. gunicorn app:myapp

Solution

1. Step 1: Understand Gunicorn command syntax

   The syntax is gunicorn module:app, where module is the Python file or package and app is the Flask app object.

2. Step 2: Apply syntax to given names

   Given the module is myapp and the app object is app, the correct command is gunicorn myapp:app.

3. Final Answer:

   gunicorn myapp:app -> Option A

4. Quick Check:

   Use colon between module and app = B [OK]

Hint: Use colon between module and app name in command [OK]

Common Mistakes:

• Using dot instead of colon
• Swapping module and app names
• Omitting the app object name

3. Given the command gunicorn -w 3 -b 0.0.0.0:8000 myapp:app, what will happen when you run it?

medium

A. Gunicorn will start 3 worker processes and listen on all network interfaces at port 8000

B. Gunicorn will start 1 worker and listen only on localhost at port 8000

C. Gunicorn will start 3 workers but listen only on localhost at default port 5000

D. Gunicorn will fail because the binding address is invalid

Solution

1. Step 1: Analyze the command options

   The -w 3 option sets 3 workers. The -b 0.0.0.0:8000 binds the server to all interfaces on port 8000.

2. Step 2: Understand the effect of binding and workers

   Binding to 0.0.0.0 means accessible from any network interface, and 3 workers allow handling multiple requests concurrently.

3. Final Answer:

   Gunicorn will start 3 worker processes and listen on all network interfaces at port 8000 -> Option A

4. Quick Check:

   -w sets workers, -b sets bind address = A [OK]

Hint: -w sets workers, -b sets bind address and port [OK]

Common Mistakes:

• Assuming default port 5000 is used
• Thinking 0.0.0.0 is invalid
• Confusing workers with threads

4. You tried to run gunicorn myapp.app but got an error saying module not found. What is the likely cause?

medium

A. The Flask app must be run with flask run only

B. You used a dot instead of a colon between module and app

C. You need to run Gunicorn inside a virtual environment

D. Gunicorn requires the app to be named 'application' not 'app'

Solution

1. Step 1: Check Gunicorn command syntax

   Gunicorn expects module:app with a colon, not a dot.

2. Step 2: Identify error cause

   Using a dot like myapp.app makes Gunicorn look for a module named myapp.app, causing module not found error.

3. Final Answer:

   You used a dot instead of a colon between module and app -> Option B

4. Quick Check:

   Use colon, not dot, in Gunicorn command [OK]

Hint: Use colon, not dot, between module and app in command [OK]

Common Mistakes:

• Using dot instead of colon
• Assuming app name must be 'application'
• Thinking virtual environment causes this error

5. You want to deploy a Flask app with Gunicorn on a server with 4 CPU cores. Which Gunicorn configuration is best to maximize performance without overloading the server?

hard

A. Run Gunicorn with 8 workers and bind to 0.0.0.0:80

B. Run Gunicorn with 1 worker and bind to 0.0.0.0:5000

C. Run Gunicorn with 2 workers and bind to 0.0.0.0:8080

D. Run Gunicorn with 4 workers and bind to 127.0.0.1:8000 behind a reverse proxy

Solution

1. Step 1: Match workers to CPU cores

   Best practice is to run Gunicorn with number of workers equal to CPU cores (4 here) for optimal concurrency.

2. Step 2: Bind to localhost and use reverse proxy

   Binding to 127.0.0.1:8000 and placing a reverse proxy (like Nginx) in front is a common production setup for security and performance.

3. Final Answer:

   Run Gunicorn with 4 workers and bind to 127.0.0.1:8000 behind a reverse proxy -> Option D

4. Quick Check:

   Workers = CPU cores, bind localhost + proxy = C [OK]

Hint: Match workers to CPU cores; use localhost bind with reverse proxy [OK]

Common Mistakes:

• Using too many workers causing overload
• Binding directly to port 80 without proxy
• Using too few workers limiting performance