See this StackOverflow question for the full problem.
I think eventstore may help, but I'm not sure if this package does anything transparently... If it doesn't, I guess it should at least provide means for the application to do so.
There should be a way to get the last logged event (per stream) out of the client upon shutdown, and this package should pass it to the application for it to save it somewhere. Similarly, upon connection, there should be a way to feed in ID(s) saved from a previous application run, to allow event handlers and sagas to resume as if nothing had happened.
I see there is a catchup subscription type, which seems close to what I need, except that it always starts at the first event in the stream, making startups very inefficient and error prone... There should be some way to let the stream start at an earlier point.
In order to properly match unfinished sagas, I guess a different rxjs like API may be needed to let this package know where the cutoff point is... I for one would be OK with that. EventStore has an API for user defined projections... Maybe use that as a starting point?
See this StackOverflow question for the full problem.
I think eventstore may help, but I'm not sure if this package does anything transparently... If it doesn't, I guess it should at least provide means for the application to do so.
There should be a way to get the last logged event (per stream) out of the client upon shutdown, and this package should pass it to the application for it to save it somewhere. Similarly, upon connection, there should be a way to feed in ID(s) saved from a previous application run, to allow event handlers and sagas to resume as if nothing had happened.
I see there is a catchup subscription type, which seems close to what I need, except that it always starts at the first event in the stream, making startups very inefficient and error prone... There should be some way to let the stream start at an earlier point.
In order to properly match unfinished sagas, I guess a different rxjs like API may be needed to let this package know where the cutoff point is... I for one would be OK with that. EventStore has an API for user defined projections... Maybe use that as a starting point?