This repository has been archived by the owner on Jun 1, 2021. It is now read-only.
Use timeouts in event sourcing protocol #176
Comments
krasserm
changed the title
krasserm
added a commit
that referenced
this issue
Dec 31, 2015
re #176 - Write request timeouts (without using akka.patterns.ask) - Write replies and Written messages applied in correct order - Major configuration schema changes (prepeare for load/read timeouts) fixes #182 - EventsourcedView uses default stash for internal and user stash operations (time-separation: recovery vs. live) - EventsourcedActor used a hierarchical stash for internal and user stash operations (space-separation: internal vs. user)
krasserm
added a commit
that referenced
this issue
Jan 7, 2016
closes #176 - Timeout for loading and saving snapshots - Timeout for event batch replay (pull-based) - Timeout for Write requests (without using akka.patterns.ask) - Write replies and Written messages applied in correct order - Major configuration schema changes fixes #182 - EventsourcedView uses default stash for internal and user stash operations (time-separation: recovery vs. live) - EventsourcedActor used a hierarchical stash for internal and user stash operations (space-separation: internal vs. user)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment, the communication between
Eventsourced*andEventLogdoesn't use timeouts. This shall be changed using anask-based communication (comparable to theReplicator-EventLogcommunication). Furthermore, these changes allow an implementation of chunked replay directly inEventsourcedView(by making repeated batch-read requests) so that theChunkedEventReplayactor can be removed and the storage provider interface for event replay simplified. This is a prerequisite for #173.The text was updated successfully, but these errors were encountered: