docs: define repository pattern boundary
This commit is contained in:
+8
-2
@@ -125,9 +125,15 @@ Project-specific DTO rules:
|
||||
|
||||
## Repository Rules
|
||||
|
||||
Repositories, gateways, or data access abstractions should express persistence
|
||||
intent without hiding important consistency behavior.
|
||||
Use the repository pattern as the default persistence boundary.
|
||||
|
||||
Repositories, gateways, or data access abstractions should express domain
|
||||
persistence intent without hiding important consistency behavior.
|
||||
|
||||
- Define repository interfaces at the application or domain boundary.
|
||||
- Implement repositories in infrastructure or persistence-specific modules.
|
||||
- Prefer specific repositories such as `OrderRepository` or
|
||||
`SupportRequestRepository`.
|
||||
- Keep query methods specific enough to reveal purpose.
|
||||
- Avoid generic repositories when they obscure domain behavior.
|
||||
- Document transaction boundaries.
|
||||
|
||||
Reference in New Issue
Block a user