Application factory pattern in Flask - Step-by-Step Execution

Concept Flow - Application factory pattern

Define create_app function

↓

Inside create_app: Create Flask app instance

↓

Configure app settings

↓

Register blueprints and extensions

↓

Return app instance

↓

Call create_app() to get configured app

↓

Run or test the app

The application factory pattern defines a function that creates and configures a Flask app instance, then returns it for use.

Execution Sample

Flask

from flask import Flask

def create_app():
    app = Flask(__name__)
    app.config['DEBUG'] = True
    @app.route('/')
    def home():
        return 'Hello, Flask!'
    return app

This code defines a function that creates a Flask app, sets debug mode, adds a home route, and returns the app.

Execution Table

Step	Action	Evaluation	Result
1	Call create_app()	Function starts	New Flask app instance created
2	Set app.config['DEBUG'] = True	Config updated	Debug mode enabled
3	Define route '/' with home()	Route registered	Home route ready
4	Return app	Function ends	Configured app instance returned
5	Run app.run()	App starts running	Server listens for requests
6	Request to '/' route	home() called	Response: 'Hello, Flask!'
7	End	No more steps	Execution stops

💡 Execution stops after app runs and handles requests or program ends.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
app	undefined	Flask instance created	Debug=True set	Route '/' added	Returned configured app

Key Moments - 3 Insights

Why do we define the app inside a function instead of at the top level?

Defining the app inside create_app delays creation until called, allowing different configs or tests. See execution_table step 1 where create_app is called to create the app.

How does the route get registered if it's inside the function?

The route decorator runs when create_app is called, adding the route to the app instance before returning it. See execution_table step 3.

What happens if we call create_app multiple times?

Each call creates a new, separate Flask app instance with its own config and routes. This supports testing or multiple app versions.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'app' after Step 2?

A App instance created but debug mode not set

B App instance not created yet

C App instance created with debug mode enabled

D App instance created with routes registered

💡 Hint

Check variable_tracker column 'After Step 2' and execution_table Step 2

At which step does the home route get registered to the app?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look at execution_table Step 3 where route '/' is registered

If we call create_app() twice, what happens to the 'app' variable each time?

A A new app instance is created each time

B App instance is destroyed after first call

C Same app instance is reused

D App instance is shared globally

💡 Hint

Refer to key_moments about multiple calls creating separate instances

Concept Snapshot

Application factory pattern in Flask:
- Define a function create_app() that creates and configures the app.
- Inside, create Flask instance, set config, register routes/blueprints.
- Return the app instance.
- Call create_app() to get a ready-to-use app.
- Supports flexible config and testing.

Full Transcript

The application factory pattern in Flask means defining a function named create_app that creates a Flask app instance when called. Inside this function, the app is created, configured, and routes or blueprints are registered. Then the app instance is returned. This delays app creation until needed, allowing different configurations or easier testing. When create_app is called, it creates a new app, sets debug mode, adds a home route, and returns the configured app. Running the app starts the server, and requests to routes call the registered functions. Calling create_app multiple times creates separate app instances. This pattern helps organize Flask apps cleanly and flexibly.

Practice

1. What is the main purpose of the application factory pattern in Flask?

easy

A. To create the Flask app inside a function for better flexibility and configuration

B. To write all routes directly in the main script without functions

C. To avoid using blueprints in the application

D. To hardcode configuration values in the app instance

Solution

1. Step 1: Understand the pattern's purpose

   The application factory pattern creates the Flask app inside a function instead of globally. This allows creating multiple app instances with different settings.

2. Step 2: Compare options to the pattern's goal

   The other options contradict the flexibility and organization benefits of the pattern. Only "To create the Flask app inside a function for better flexibility and configuration" correctly describes the main purpose.

3. Final Answer:

   To create the Flask app inside a function for better flexibility and configuration -> Option A

4. Quick Check:

   Application factory = create app in function [OK]

Hint: Remember: factory means create inside a function [OK]

Common Mistakes:

• Thinking app is created globally, not inside a function
• Confusing blueprints with the factory pattern
• Assuming configuration is hardcoded, not flexible

2. Which of the following is the correct way to define an application factory function in Flask?

easy

A. def create_app():\n return Flask

B. app = Flask(__name__)\ndef create_app():\n return app

C. def create_app():\n app = Flask(__name__)\n return app

D. def create_app():\n app = Flask\n return app

Solution

1. Step 1: Check function definition and app creation

   def create_app():\n app = Flask(__name__)\n return app correctly defines a function named create_app that creates a Flask instance and returns it.

2. Step 2: Identify syntax errors or incorrect returns

   app = Flask(__name__)\ndef create_app():\n return app creates app outside the function, which is not factory pattern. def create_app():\n return Flask returns the Flask class, not an instance. def create_app():\n app = Flask\n return app tries to assign Flask class without parentheses, causing error.

3. Final Answer:

   def create_app():\n app = Flask(__name__)\n return app -> Option C

4. Quick Check:

   Factory function creates and returns app instance [OK]

Hint: Factory returns a new Flask instance inside a function [OK]

Common Mistakes:

• Returning the Flask class instead of an instance
• Creating app outside the factory function
• Missing parentheses when creating Flask instance

3. Given this code snippet using the application factory pattern, what will print(app.config['DEBUG']) output?

def create_app():
    app = Flask(__name__)
    app.config['DEBUG'] = True
    return app

app = create_app()
print(app.config['DEBUG'])

medium

A. False

B. True

C. None

D. KeyError

Solution

1. Step 1: Trace the factory function execution

   The function create_app creates a Flask app and sets app.config['DEBUG'] = True before returning the app.

2. Step 2: Check the printed config value

   After calling create_app(), the returned app has DEBUG set to True. So printing it outputs True.

3. Final Answer:

   True -> Option B

4. Quick Check:

   Config DEBUG set True, print shows True [OK]

Hint: Config set inside factory is available after creation [OK]

Common Mistakes:

• Assuming default DEBUG is False without setting
• Expecting KeyError if config key is missing (it's set here)
• Confusing app instance with factory function

4. Identify the error in this application factory code:

def create_app():
    app = Flask(__name__)
    @app.route('/')
    def home():
        return 'Hello'
    return app

app = create_app()
app.run()

medium

A. Missing parentheses in Flask constructor

B. Calling app.run() outside the factory is incorrect

C. Route decorator used incorrectly inside factory

D. No error; code runs correctly

Solution

1. Step 1: Review the factory function structure

   The function creates a Flask app, defines a route inside it, and returns the app instance.

2. Step 2: Check usage of app.run()

   Calling app.run() outside the factory is normal to start the server. The code is valid and will run correctly.

3. Final Answer:

   No error; code runs correctly -> Option D

4. Quick Check:

   Defining routes inside factory and running app outside is valid [OK]

Hint: Routes can be inside factory; run app after creation [OK]

Common Mistakes:

• Thinking app.run() must be inside factory
• Assuming route decorators can't be inside factory
• Confusing Flask constructor syntax

5. You want to create a Flask app using the application factory pattern that registers a blueprint and initializes an extension. Which code snippet correctly applies this pattern?

hard

A. def create_app():
app = Flask(__name__)
from .views import main_bp
app.register_blueprint(main_bp)
from flask_sqlalchemy import SQLAlchemy
db = SQLAlchemy()
db.init_app(app)
return app

B. app = Flask(__name__)
from .views import main_bp
app.register_blueprint(main_bp)
from flask_sqlalchemy import SQLAlchemy
db = SQLAlchemy(app)

C. def create_app():
app = Flask(__name__)
from .views import main_bp
app.register_blueprint(main_bp)
from flask_sqlalchemy import SQLAlchemy
db = SQLAlchemy(app)
return app

D. def create_app():
app = Flask(__name__)
from .views import main_bp
main_bp.register_blueprint(app)
from flask_sqlalchemy import SQLAlchemy
db = SQLAlchemy(app)
return app

Solution

1. Step 1: Understand blueprint registration

   Blueprints are registered on the app using app.register_blueprint(). Two options do this correctly, while one incorrectly calls main_bp.register_blueprint(app).

2. Step 2: Check extension initialization

   For extensions like SQLAlchemy, the recommended pattern is to instantiate the extension without the app (db = SQLAlchemy()) and then call db.init_app(app). The option that does db = SQLAlchemy(); db.init_app(app) follows this correctly. The other factory option with correct blueprint registration uses db = SQLAlchemy(app), which binds it directly to the app and is less flexible.

3. Final Answer:

   def create_app(): app = Flask(__name__) from .views import main_bp app.register_blueprint(main_bp) from flask_sqlalchemy import SQLAlchemy db = SQLAlchemy() db.init_app(app) return app -> Option A

4. Quick Check:

   Blueprint registered on app; extension initialized with init_app [OK]

Hint: Register blueprints on app; init extensions with init_app(app) [OK]

Common Mistakes:

• Registering blueprint on blueprint instead of app
• Creating extension with app inside factory instead of init_app
• Not importing blueprint inside factory function