These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
EventsourcedWriter(see also this architectural overview). When a writer is started it automatically subscribes to changes in an event log. You can find further details in the API docs. Not sure if I understood your question regarding atomicity. Eventuate batch-writes event atomically to the storage backend(s). These writes are idempotent and the storage order is consistent with causal event order (see this section in the docs). So, consumers (including
EventsourcedWriters) see a de-duplicated, causally-ordered event stream when reading from the log.
does EventsourcedWriter reads event logs periodically from the storage backend?
Eventuate pushes events to event-sourced writers/actors/views/... after having successfully written them at a location or replicated from other locations i.e. these actors consume events with minimal latency. This is independent of the chosen storage backend.