Services - Feather

Services hold the business logic. Routes should stay thin enough to read at a glance, and anything more than parsing a request and returning a response belongs here.

services/user_service.py

from feather import Service, transactional
from feather.exceptions import ValidationError, ConflictError
from feather.db import paginate
from models import User

class UserService(Service):
    @transactional  # commits on success, rolls back on exception
    def create(self, email: str, username: str) -> User:
        if not email or '@' not in email:
            raise ValidationError('Valid email required', field='email')

        if User.query.filter_by(email=email).first():
            raise ConflictError('Email already registered')

        user = User(email=email, username=username)
        self.db.add(user)
        return user

    def list_paginated(self, page: int = 1, per_page: int = 20):
        query = User.query.order_by(User.created_at.desc())
        return paginate(query, page=page, per_page=per_page)

Transactions

@transactional commits when the method returns and rolls back when it raises. Since exceptions already map to HTTP responses, a validation failure rolls back the transaction and returns a 400 with no explicit handling.

Injecting a service into a route

@api.post('/users')
@inject(UserService)
def create_user(user_service, email: str, username: str):
    user = user_service.create(email=email, username=username)
    return {'user': user}, 201

Singleton services

For initialization that should happen once rather than per request:

from feather.services import singleton, Service

@singleton
class CacheService(Service):
    def __init__(self):
        super().__init__()
        self.cache = {}  # shared across all requests

Generating a service

feather generate service PostService