0The service layer pattern helps organize your Flask app by keeping business logic separate from routes. It makes your code cleaner and easier to manage.
class ServiceLayer: def __init__(self, repository): self.repository = repository def perform_action(self, data): # business logic here processed = data.upper() self.repository.save(processed) return processed
The service layer is usually a class that holds business logic methods.
It often uses a repository or data access layer to handle database operations.
class UserService: def __init__(self, user_repo): self.user_repo = user_repo def create_user(self, username): username = username.strip().lower() self.user_repo.add(username) return f"User {username} created"
class OrderService: def __init__(self, order_repo): self.order_repo = order_repo def place_order(self, order_data): # validate order if not order_data.get('items'): raise ValueError('No items in order') self.order_repo.save(order_data) return 'Order placed successfully'
This Flask app uses a service layer to handle user creation logic. The route calls the service, which processes the username and saves it via the repository. The repository stores users in memory.
from flask import Flask, request, jsonify app = Flask(__name__) class UserRepository: def __init__(self): self.users = [] def add(self, username): self.users.append(username) def list_all(self): return self.users class UserService: def __init__(self, user_repo): self.user_repo = user_repo def create_user(self, username): username = username.strip().lower() self.user_repo.add(username) return username user_repo = UserRepository() user_service = UserService(user_repo) @app.route('/users', methods=['POST']) def add_user(): data = request.json username = data.get('username', '') if not username: return jsonify({'error': 'Username is required'}), 400 user = user_service.create_user(username) return jsonify({'message': f'User {user} created'}) @app.route('/users', methods=['GET']) def get_users(): users = user_repo.list_all() return jsonify({'users': users}) if __name__ == '__main__': app.run(debug=True)
Keep your service layer focused on business rules, not HTTP details.
Use the service layer to make your routes simpler and easier to read.
Testing services separately from routes helps catch bugs early.
The service layer separates business logic from Flask routes.
It improves code organization, reuse, and testing.
Use it when your app logic grows beyond simple route handlers.
service layer in a Flask application?get_user_by_id inside a Flask route?service.get_user_by_id(id) is correct.user = get_user_by_id(id) misses the service prefix, B uses invalid arrow syntax (->) for Python, C uses wrong dot notation./user/2 if user with ID 2 exists?
from flask import Flask, jsonify
app = Flask(__name__)
class UserService:
def get_user_by_id(self, user_id):
users = {1: 'Alice', 2: 'Bob'}
return users.get(user_id, None)
service = UserService()
@app.route('/user/<int:user_id>')
def user(user_id):
user_name = service.get_user_by_id(user_id)
if user_name:
return jsonify({'user': user_name})
else:
return jsonify({'error': 'User not found'}), 404
get_user_by_id(2) returns 'Bob'.from flask import Flask, jsonify
app = Flask(__name__)
class UserService:
def get_user(self, user_id):
return None
service = UserService()
@app.route('/user/<int:user_id>')
def user(user_id):
user = service.get_user(user_id)
if user:
return jsonify({'user': user})
else:
return jsonify({'error': 'User not found'})
get_user method always returns None, so user is always None in the route.user is None, the route always returns the error JSON, meaning no user is ever found.create_user that saves a user and returns the new user ID. Which approach best follows the service layer pattern in Flask?create_user to the service class and calls it from the route, following the pattern.Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.