Timeline for Confused about commands, domain events and external events in event sourcing
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2024 at 14:17 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 |
added 8 characters in body
|
| Jun 27, 2020 at 14:51 | comment | added | Maciej Pszczolinski | The first domain event of an aggregate usually be "AggregateCreated", e.g. "CustomerRegistered" or "OrderPlaced". | |
| Feb 6, 2019 at 20:35 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 |
added 1837 characters in body
|
| Feb 6, 2019 at 18:39 | comment | added | Andrzej Gis | If Aggregate root is the only one producing domain events, we've got a problem. The only way interact with an aggregate (and let it produce its own domain events) is by applying a domain event to it. So we need something more to produce the "first" domain event to get things started. Would it be a command handler like in the 1st case? Also you mentioned that domain events are useful to talk to other aggregates within the same domain model. I would say, a domain model is not restricted to a single microservice. Does it imply that domain events could travel from one microservice to another? | |
| Feb 6, 2019 at 3:27 | history | answered | VoiceOfUnreason | CC BY-SA 4.0 |