ddd-patterns
Installation
SKILL.md
DDD Integration Patterns
Start from bounded contexts, ownership, invariants, and failure modes. These patterns add operational and cognitive cost; use the smallest one that solves an observed force.
Decision Guide
| Force | Candidate |
|---|---|
| protect one model from another model/API | anti-corruption layer |
| atomically persist state and publish intent | transactional outbox |
| deduplicate at-least-once delivery | inbox/idempotent consumer |
| coordinate a long-running cross-context outcome | process manager or saga |
| optimize a materially different read model | CQRS |
| require event history as source of truth | event sourcing |
Do not equate CQRS with event sourcing, saga with distributed transaction, or event publication with exactly-once processing.