hseeberger/eventsourced

Event sourced entities in Rust.

eventsourced's Issues

feat: projection management API and more comprehensive error strategy

So far the initial projection support only offers a minimal ErrorStrategy (stop or retry) and no projection management at all. To be useful in production scenarios, we need:

• add ErrorStrategy::Skip,
• extend ErrorStrategy::Retry with a maximum number of retries, then stop or skip,
• offer a projection management API that allows for
  • stopping a running projection
  • resuming a stopped projection
  • set the sequence number of a stopped projection to any existing value and restart from there

naming discussion

I am not Rust developer, but I fail to understand why public API should have partial names?

I found in code import like:

evt_log::EvtLog, snapshot_store::SnapshotStore

Why omit 2 characters in words event_log and EventLog?

It is very strange, that word EventSourced is used instead of EvtSourced or worse: EvtSrcd or similar :)

[eventsourced-postgres] PostgresEvtLog.evts_by_id hangs when requesting future events

The current implementation is too naive. It will not return until the to_seq_noth event has been persisted.

Instead we need to immediately return a stream which is able to emit all current events and then continue until to_seq_no is reached.

There is just a little bug wrt sequence numbers.

Use secrecy types for sensitive data

secrecy provides various data types which safely implemnt Debug and Display such that no sensitive information can accidentally escape, e.g. via logging.

One use case is the Config struct for the eventsourced-postgres EvtLog.