docs
This commit is contained in:
@@ -196,15 +196,16 @@ Avoid CQRS Light when:
|
||||
|
||||
⸻
|
||||
|
||||
12. Migration Path
|
||||
12. Adoption Rule (Strict)
|
||||
|
||||
CQRS Light allows incremental adoption:
|
||||
1. Start with classic Clean Architecture
|
||||
2. Separate commands and queries logically
|
||||
3. Optimize read paths as needed
|
||||
4. Introduce events or projections later (optional)
|
||||
CQRS Light is a structural rule inside Core.
|
||||
|
||||
No rewrites required.
|
||||
If CQRS Light is used:
|
||||
|
||||
- commands and queries MUST be separated by responsibility
|
||||
- queries MUST remain read-only and must not enforce invariants
|
||||
|
||||
This document does not define a migration plan.
|
||||
|
||||
⸻
|
||||
|
||||
@@ -241,4 +242,4 @@ Without:
|
||||
• Event sourcing complexity
|
||||
• Premature optimization
|
||||
|
||||
It is the safest way to gain CQRS benefits while staying true to Clean Architecture.
|
||||
It is the safest way to gain CQRS benefits while staying true to Clean Architecture.
|
||||
|
||||
Reference in New Issue
Block a user