repository-adapters

To map database errors to domain errors, implement an adapter at the repository edge that translates DB-level exceptions into domain-specific errors before they cross the boundary. This preserves domain integrity by isolating persistence concerns from the domain layer.

A repository adapter is a structural bridge connecting database repository patterns to stable domain interfaces. You need one when updating repository methods or coordinating multiple SQL dialects to ensure the domain boundary remains protected from infrastructure changes.

Supporting multiple SQL dialects requires guiding generated query layers and tests through change-safe patterns at the adapter boundary. The adapter coordinates dialect-specific queries while exposing a stable repository interface to the domain layer.

To update repository methods safely, review the domain interface, adjust the adapter implementation, and validate generated query layers and tests. This ensures correct error handling and safe workflows while maintaining the established domain boundary contract.

The repository pattern works with domain-driven design by defining a stable adapter boundary that callers rely on. It aligns repository-layer changes with domain boundaries, ensuring DB errors are translated and infrastructure concerns do not leak into the domain.