One of the most common mistakes when starting with Domain Events and with DDD in general is to not go the whole way and figure our what is actually going on in the domain. It is easy to fall into the trap of naming all events SomethingCreated, SomethingUpdated and SomethingDeleted. While not a problem in itself it does not make use of the powerful thing we get by adding the context and meaning to the actual change that the Domain Event represent. You lose the intent of the event and reading the event log later will not provide that much value.
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