These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
@krasserm About RBMHTechnology/eventuate#68 you say:
Should an application still decide to replicate state within a location and concurrent updates are made to these replicas, these updates may be reported as causally related updates which boils down to a last-writer-wins conflict resolution strategy.
When state replication occurs within a location? I want to understand in wich cases we can end up with a last-writer-wins resolution of concurrent updates.
Also, IMHO the explanation in that issue should be explicit (currently there is a link to the issue) in the documentation because is very useful.