advanced-alchemy

You can use built-in repository and service layers to implement async SQLAlchemy CRUD operations, which provide lifecycle hooks for business logic and eliminate repetitive data access boilerplate across FastAPI, Litestar, and other frameworks.

The best way to implement the repository pattern and service layer is by using opinionated base models and async CRUD operations with lifecycle hooks, which automatically handle data access code and business logic separation for SQLAlchemy-backed web applications.

Yes, you can automatically manage Alembic migrations and database sessions, as the Skill provides first-party plugins with automatic session and transaction management for Litestar, FastAPI, Flask, Sanic, and Starlette.

Yes, the SQLAlchemy service layer supports multiple Python web frameworks besides Litestar, offering first-party plugins with dependency injection and session management for FastAPI, Flask, Sanic, and Starlette.

You can generate SQLAlchemy models with audit trails and UUID primary keys by using opinionated base models, which provide auto-generated IDs, audit timestamps, and mixins for slugs, unique constraints, and optimistic locking.

The limitations of using built-in repository and service layers for async CRUD operations are not explicitly documented, but the approach is highly opinionated, meaning developers must adapt to its specific base models, lifecycle hooks, and cross-database compatibility constraints.