These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
PersistentActors in Akka Persistence cannot be replicated and must be singletons. This allows for strong/sequential consistency of actor state but with limited write availability during network partitions. Eventuate additionally supports availability zones (locations) which can be data centers, temporarily connected devices, nodes in a cluster, etc.
EventsourcedActors can be replicated across locations and are writable at multiple locations (multi-master). They even remain available for writes even during network partitions (high availability). To make this possible consistency of replicated actors must be relaxed to causal consistency (the strongest consistency that is still compatible with AP from CAP). Event causality is tracked with vector clocks.
EventsourcedActorreplication is just a special case of
EventsourcedActorcollaboration on a shared (replicated) event log. In that case,
EventsourcedActors of different type can collaborate to implement a reliable, distributed business process, for example. Reliable and idempotent event distribution to collaborators is a core feature of a replicated event log.