backend-engineering

Structure a FastAPI project using clean architecture by enforcing layered separation across API endpoints, Service business logic, Repository data access, and SQLAlchemy Models. This separation of concerns ensures maintainable and scalable backend services.

Implement the repository pattern with SQLAlchemy by isolating database operations within a dedicated Repository layer, separate from business logic. This Skill provides conventions for structuring repository implementations alongside SQLAlchemy models and Pydantic schemas.

The best way to create a new API endpoint is to follow established conventions for defining routes, request/response Pydantic schemas, service logic, and SQLAlchemy database models. This process ensures robust and maintainable API endpoint creation.

Yes, Pydantic schemas are needed to define request and response structures within the API layer. This Skill guides you through creating these schemas to maintain a clear boundary between data validation and internal business logic.

Separate service logic from API routes in FastAPI when applying clean architecture to maintain separation of concerns. Keeping business logic in a dedicated Service layer prevents endpoint clutter and ensures backend services remain maintainable.