Service layer pattern in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a service class method that returns a greeting message.

Flask

class GreetingService:
    def get_greeting(self):
        return [1]

Drag options to blanks, or click blank then click option'

Aprint("Hello")

B"Hello from service!"

Creturn "Hi"

DHello

Attempts:

3 left

💡 Hint

Common Mistakes

Using print instead of return

Not using quotes around the string

The method should return a string greeting. Option B correctly returns the string.

2fill in blank

medium

Complete the Flask route to call the service method and return its result.

Flask

from flask import Flask
app = Flask(__name__)

service = GreetingService()

@app.route('/')
def home():
    return [1]

Drag options to blanks, or click blank then click option'

Aservice.get_greeting

BGreetingService.get_greeting()

Cservice.get_greeting()

Dget_greeting()

Attempts:

3 left

💡 Hint

Common Mistakes

Returning the method itself without calling it

Calling the method on the class instead of the instance

The route function must call the service method with parentheses to get the greeting string.

3fill in blank

hard

Fix the error in the service method to accept a name parameter and return a personalized greeting.

Flask

class GreetingService:
    def get_greeting(self, [1]):
        return f"Hello, {name}!"

Drag options to blanks, or click blank then click option'

Aname

Bself

Cusername

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using a parameter name different from the one used in the string

Forgetting to add the parameter

The method must accept a parameter named 'name' to use it in the greeting string.

4fill in blank

hard

Fill both blanks to update the Flask route to accept a name URL parameter and pass it to the service.

Flask

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

service = GreetingService()

@app.route('/hello/<[1]>')
def hello():
    name = request.view_args.get('[2]')
    return service.get_greeting(name)

Drag options to blanks, or click blank then click option'

Aname

Buser

Dusername

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the URL parameter and the key in view_args

Forgetting to include the URL parameter in the route

The URL parameter and the key to get it from view_args must both be 'name' to match.

5fill in blank

hard

Fill all three blanks to create a service method that validates input and returns a message accordingly.

Flask

class GreetingService:
    def get_greeting(self, name):
        if not name or len(name) [1] 0:
            return [2]
        return f"Hello, {name}[3]"

Drag options to blanks, or click blank then click option'

A<=

B"Hello, Guest!"

C!"

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong comparison operator

Not returning a default message for empty name

Forgetting punctuation in the greeting

The method checks if name is empty or length is less or equal to zero, returns a default greeting, else returns personalized greeting with exclamation.

Practice

1. What is the main purpose of using a service layer in a Flask application?

easy

A. To serve static files like images and CSS

B. To separate business logic from route handlers for better organization

C. To handle database migrations automatically

D. To manage user sessions and cookies

Solution

1. Step 1: Understand the role of service layer

   The service layer is designed to hold business logic separate from Flask routes, making code cleaner and easier to maintain.

2. Step 2: Compare with other options

   Handling migrations, serving static files, and managing sessions are not the service layer's responsibilities.

3. Final Answer:

   To separate business logic from route handlers for better organization -> Option B

4. Quick Check:

   Service layer = separates business logic [OK]

Hint: Service layer = business logic outside routes [OK]

Common Mistakes:

• Confusing service layer with database or session management
• Thinking service layer serves static files
• Assuming service layer handles HTTP requests directly

2. Which of the following is the correct way to call a service function get_user_by_id inside a Flask route?

easy

A. user = get_user_by_id(id)

B. user = service->get_user_by_id(id)

C. user = service.get_user_by_id(id)

D. user = get_user_by_id.service(id)

Solution

1. Step 1: Understand typical service layer usage

   Service functions are usually grouped in a service object or module, so calling service.get_user_by_id(id) is correct.

2. Step 2: Identify syntax errors in other options

   user = get_user_by_id(id) misses the service prefix, B uses invalid arrow syntax (->) for Python, C uses wrong dot notation.

3. Final Answer:

   user = service.get_user_by_id(id) -> Option C

4. Quick Check:

   Call service function with dot notation [OK]

Hint: Call service functions as service.function(args) [OK]

Common Mistakes:

• Calling service functions without service prefix
• Using invalid syntax like arrows (->)
• Misplacing dot notation

3. Given this Flask route and service layer code, what will be the output when accessing /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

medium

A. {"error": "User not found"}

B. Server error due to missing user

C. 404 Not Found error without JSON

D. {"user": "Bob"}

Solution

1. Step 1: Check user existence in service

   User with ID 2 exists in the dictionary as 'Bob', so get_user_by_id(2) returns 'Bob'.

2. Step 2: Analyze route response

   Since user_name is truthy, route returns JSON with {'user': 'Bob'} and status 200.

3. Final Answer:

   {"user": "Bob"} -> Option D

4. Quick Check:

   User found returns JSON with user name [OK]

Hint: If user exists, route returns JSON with user name [OK]

Common Mistakes:

• Assuming 404 error when user exists
• Confusing JSON error message with missing user
• Thinking server error occurs without exception

4. Identify the error in this Flask route using a service layer:

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'})

medium

A. The service method always returns None, so user is never found

B. The route decorator syntax is incorrect

C. Missing return statement in the else block

D. Flask app is not instantiated properly

Solution

1. Step 1: Analyze service method return value

   The get_user method always returns None, so user is always None in the route.

2. Step 2: Understand route behavior

   Because user is None, the route always returns the error JSON, meaning no user is ever found.

3. Final Answer:

   The service method always returns None, so user is never found -> Option A

4. Quick Check:

   Service returns None means no user found [OK]

Hint: Check service method return values carefully [OK]

Common Mistakes:

• Assuming route decorator is wrong
• Missing return in else block (actually present)
• Thinking Flask app is not created properly

5. You want to add a new service method create_user that saves a user and returns the new user ID. Which approach best follows the service layer pattern in Flask?

medium

A. Add create_user method in service class and call it from route

B. Write database code directly in the route

C. Put user creation logic in app initialization

D. Use global variable in route without service

Solution

1. Step 1: Recall service layer purpose

   The service layer should contain business logic like user creation, keeping routes simple and clean.

2. Step 2: Evaluate options

   Add create_user method in service class and call it from route correctly adds create_user to the service class and calls it from the route, following the pattern.

3. Final Answer:

   Add create_user method in service class and call it from route -> Option A

4. Quick Check:

   Business logic in service, routes call service [OK]

Hint: Put business logic in service, call from routes [OK]

Common Mistakes:

• Putting logic directly in routes
• Using global variables instead of service
• Placing logic in app initialization