These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
all Spring nodes of course should see the same state / use the same data where state divergence should be avoided if possible
With divergence allowed I mean if temporary divergence should be allowed. Of course, replicated state should eventually converge. If you allow temporary divergence e.g. making potentially conflicting updates during partitions you need to resolve conflicts later. This is compatible with AP of CAP and where Eventuate fits in. A special application of automated conflict resolution are CRDTs. On the other hand, if you want to prevent temporary divergence of replicated state (so that you don't have to resolve conflict later), you need coordination which is not compatible with AP of CAP i.e. you sacrifice availability for stronger consistency of replicated state. If you want to achieve that, Eventuate is not what you want.
if Eventuate will work as expected if I have a running instance of Eventuate in multiple Spring application deployed on multiple nodes which share a single Cassandra backend
yes, that's possible for testing. Each Spring node should use its own keyspace in the shared Cassandra cluster then. Alternatively, you could also use a LevelDB storage backend at each location, making deployment even more lightweight.