domain-events
Règle 06 : Domain Events. Use when implementing DDD patterns.
When & Why to Use This Skill
This Claude skill provides expert guidelines and best practices for implementing Domain Events within Domain-Driven Design (DDD) patterns. It helps developers and architects design decoupled, scalable systems by effectively capturing and communicating significant business state changes across different bounded contexts.
Use Cases
- Decoupling Microservices: Use domain events to trigger side effects in external services without creating direct dependencies between modules.
- Implementing Eventual Consistency: Maintain data integrity across distributed systems by propagating changes through events rather than synchronous transactions.
- Asynchronous Task Execution: Offload non-critical operations, such as sending emails or generating reports, to background processes triggered by domain events.
- Audit Logging and System Observability: Create a reliable record of significant business transitions to improve traceability and simplify debugging in complex architectures.
| name | domain-events |
|---|---|
| description | Règle 06 : Domain Events. Use when implementing DDD patterns. |
Règle 06 : Domain Events
This skill provides guidelines and best practices.
See @REFERENCE.md for detailed documentation.