We, the Eventuate committers, are pleased to announce the availability of Eventuate 0.4. Eventuate is a toolkit for building distributed, highly-available and partition-tolerant event-sourced applications. It is written in Scala and built on top of Akka, a toolkit for building highly concurrent, distributed, and resilient message-driven applications on the JVM. Eventuate

• derives current application state from logged events (event sourcing)
• replicates application state by replicating events across multiple locations
• allows updates to replicated state at multiple locations concurrently (multi-master)
• allows individual locations to continue writing even if they are partitioned from other locations
• provides means to detect, track and resolve conflicting updates (interactive and automated)
• enables reliable event collaboration between event-sourced microservices
• enables applications to implement a causal consistency model
• preserves causal ordering of replicated events
• provides implementations of operation-based CRDTs
• supports distribution up to global scale

A more detailed introduction is given in the following documentation sections:

• Introduction
• Architecture

For getting started with Eventuate, take a look at:

• User guide
• Example application

New features and enhancements in Eventuate 0.4 include:

• Support for cyclic replication networks (based on a complete re-write of the event replication mechanism)
• Disaster recovery of replication endpoints
• Disaster recovery example implementation
• Event replay backpressure
• CRDT instance snapshots
• Lazy load and recovery of CRDT instances
• LWW-Register CRDT
• Isolation of Cassandra log and index reads
• Reference documentation TOC expanded
• Example application startup scripts enhancements
  • bug fix for running on Linux
  • automated classpath generation

You can find further details in the release notes. If you have any questions or comments, please let us know.