fastapi-backend-guidelines

Structure a FastAPI backend using Domain-Driven Design by organizing code into a layered Router-Service-Repository architecture. This pattern separates routing, business logic, and data access to ensure robust, scalable, and maintainable API development.

Manage async database operations in FastAPI by applying async/await best practices throughout the stack with SQLModel or SQLAlchemy ORM. This approach ensures efficient, non-blocking database interactions within your service and repository layers.

Yes, you can use SQLModel for ORM and data validation in a FastAPI project. The framework combines SQLAlchemy and Pydantic to facilitate robust data access, model definition, and request validation across your API's layered architecture.

Separate business logic from routing in FastAPI by implementing a Service layer between your Routers and Repositories. This architectural pattern isolates domain operations from API endpoints, improving maintainability and enforcing clear separation of concerns.

FastAPI relies on Pydantic validation to ensure robust and scalable API development. By enforcing strict data schemas through DTOs, it prevents invalid data from reaching your service layer and standardizes error handling across the application.

Generate a new domain template for a FastAPI project by applying the fastapi-backend-guidelines skill. It outputs structured definitions for models, repositories, services, DTOs, and routers, adhering to established Domain-Driven Design patterns.