Examples of things that happen that might not be suitable to model as Domain Events: Something technical (a ButtonClicked, ExceptionThrown etc) happened that we want to record or handle, but it is not described in the ubiquitous language of our domain. Something that happened outside of our bounded context. This could a Domain Event in another system or a different bounded context. Requests to your system. These we define as Commands rather than events, since they can be rejected by our system.
What are Domain Events? | DDD | Serialized
from serialized.io
Filed under:
Same Source
Related Notes
- Another way this is noted is that Factories are “pure domain”, but ...from UnknownAuthor
- The Factory should create new objects, while the Repository should ...from UnknownAuthor
- For immutable Value Objects it means that all attributes are initia...from UnknownAuthor
- An Aggregate is a group of associated objects which are considered ...from UnknownAuthor
- There are three characteristics of a Service: The operation perfor...from UnknownAuthor
- For example, to transfer money from one account to another; should ...from UnknownAuthor
- Concentrate all the code related to the domain model in one layer a...from UnknownAuthor