persistence-analyst

To audit database schema design and Drizzle ORM models, you can trigger an analysis that validates table designs, column types, indexes, and constraints. It generates a comprehensive report ensuring your schema accurately reflects the domain and adheres to best practices.

The outbox pattern ensures reliable event publishing within transaction boundaries in domain-driven design. Auditing verifies its implementation alongside aggregate roots and state machines to maintain data integrity and consistent state transitions across your persistence layer.

Checking repository pattern and multi-tenant isolation implementations involves auditing your persistence layer to verify transaction boundaries and data segregation. This process ensures state machines and soft-delete strategies are consistently enforced across tenant data.

Yes, you can review migration history and query performance for a microservice before deployment. The analysis audits your database schema and Drizzle ORM models to ensure production readiness, verifying domain models and persistence patterns.

You need to generate a persistence model for domain-driven design when validating ORM models against domain models, aggregate roots, and transaction boundaries. It ensures your database schema, soft-delete strategy, and multi-tenant isolation maintain application data layer integrity.