Service layer pattern in Flask - Step-by-Step Execution

Concept Flow - Service layer pattern

Client Request

↓

Controller/Route

↓

Service Layer

↓

Business Logic

↓

Response to Client

The client sends a request to the controller, which calls the service layer. The service layer handles business logic and interacts with data access, then returns a response.

Execution Sample

Flask

from flask import Flask, jsonify
app = Flask(__name__)

class UserService:
    def get_user(self, user_id):
        return {"id": user_id, "name": "Alice"}

@app.route('/user/<int:user_id>')
def get_user(user_id):
    service = UserService()
    user = service.get_user(user_id)
    return jsonify(user)

A Flask route calls the UserService to get user data and returns it as JSON.

Execution Table

Step	Action	Input	Service Layer Call	Output
1	Client sends GET /user/1	/user/1	N/A	N/A
2	Flask route receives request	user_id=1	UserService.get_user(1)	N/A
3	Service layer processes request	user_id=1	get_user(1)	{"id": 1, "name": "Alice"}
4	Route returns JSON response	user data	N/A	{"id": 1, "name": "Alice"}
5	Client receives response	N/A	N/A	{"id": 1, "name": "Alice"}

💡 Request handled and response sent back to client.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
user_id	N/A	1	1	1	1
service	N/A	UserService instance	UserService instance	UserService instance	UserService instance
user	N/A	N/A	{"id": 1, "name": "Alice"}	{"id": 1, "name": "Alice"}	{"id": 1, "name": "Alice"}

Key Moments - 2 Insights

Why does the controller call the service layer instead of accessing data directly?

The controller calls the service layer to keep business logic separate from routing, as shown in step 2 and 3 of the execution table.

What happens if the service layer returns no data?

If the service returns no data, the controller can handle it (e.g., return 404). This separation is clear in step 3 and 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the output of the service layer at step 3?

A {"id": 1, "name": "Alice"}

B N/A

C {"id": 2, "name": "Bob"}

D Error

💡 Hint

Check the 'Output' column at step 3 in the execution_table.

At which step does the Flask route receive the client request?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' column describing Flask route receiving request.

If the service layer returned an empty dictionary, how would the output at step 3 change?

A {"id": 1, "name": "Alice"}

B {}

C N/A

D Error

💡 Hint

Consider the 'Output' column at step 3 and what the service returns.

Concept Snapshot

Service layer pattern separates business logic from controllers.
Controller handles HTTP requests and responses.
Service layer contains business rules and data access calls.
Improves code organization and testing.
In Flask, routes call service methods to get data.
Service returns data, controller formats response.

Full Transcript

The service layer pattern organizes code by separating business logic from the controller or route handlers. When a client sends a request, the Flask route receives it and calls the service layer. The service layer processes the request, applies business rules, and fetches or modifies data. Then it returns the result to the controller, which sends the response back to the client. This separation keeps the code clean and easier to maintain. In the example, the Flask route calls UserService.get_user with the user ID, which returns user data. The route then returns this data as JSON. This pattern helps keep routing simple and business logic centralized.