Search results

Analyse what metrics can we expose about the aggregate update process. Implement

Status: Open.

#21 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Sep 14, 2022

Interface EventStoreDbOperations should be in change of only aggregate updating operations. Segregate new interface for event streams. For example we would be able to use Kafka as a backend for our event streams

Status: Open.

#17 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Aug 24, 2022

Snapshots should be versioned. Now the only last version is stored.

Status: Open.

#13 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Aug 2, 2022

Snapshots table name and frequency shouldn't be a property of the entire EventSourcing lib. We should be able to configure it in a per-aggregate manner

Status: Open.

#12 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Jul 21, 2022

streamBatchSize shouldn't be a property of the entire EventSourcing lib. We should be able to configure it in a per-stream manner

Status: Open.

#11 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Jul 21, 2022

During @SubscribeEvent processing we don't take into consideration that event handler method might be (and preferably) suspend. Suspend methods are taking extra implicit parameter which should be handled properly.

Status: Open.

#10 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Jul 13, 2022

Event store should auto generate sequential number for the events (which is used then to read events from db). It will ensure the total order over the aggregate type event log

Status: Open.

#7 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Jun 18, 2022

Implement idempotent streams subscriber

Status: Open.

#6 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Jun 18, 2022

Db operations for event sourcing should be suspend

Status: Open.

#4 In andrsuh/tiny-event-sourcing;

· andrsuh opened on Jun 18, 2022