These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
PersonRelocated. That means that you would typically not want to have a single (technical)
PersonUpdatedevent that seems to be suitable in the beginning from a technical standpoint as it typically suffices to perform your updates, but you rather want to model the events that actually happen in your domain and keep the intentions. This comes with some advantages. For example in case of concurrent events you have a much better chance to solve a conflict according to your domain's requirements. In case of two technical
PersonUpdatedevents it might be hard to tell which of the fields of the events should define the state of the write model while in case of events like
PersonMarriedit can be easy to tell there is no real conflict. These kind of semantically rich events could also give you the chance to evolve your application much better for example when building additional read models in the future that can be based on the captured intentions instead of plain update information.