These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
PersistOnEvent. If new events should be written to another event log, you probably have an
ConfirmedDeliveryhowever may deliver commands out of order and may also generate duplicates. I've not used that for
Eventsourced*component interactions in my projects so far, only for interactions with external services that are not event-sourced.
EventsourcedWriter) from updates in write models (managed by
EventsourcedActorcommunication is rather used to acieve eventual consistency between write models (having state replication as a special case here).