andrsuh/tiny-event-sourcing

Issues

• Reading event streams should only be done by one instance of the application and intercepted by another instance if the first one fails

  #32 opened a year ago by annchous
  0

• возвращать только финлог обратившегося юзера

  #35 opened 2 years ago by shinehlina
  0

• Command should be able to produce more than one event. Also consider the ability to produce zero events

  #16 opened 2 years ago by andrsuh
  1

• Investigate and publish artifacts to maven central

  #15 opened 2 years ago by andrsuh
  1

• Think of adding some embedded DB or use test container to run integration tests

  #22 opened 2 years ago by andrsuh
  1

• Learn about open source licenses, present, choose the most suitable and integrate

  #19 opened 2 years ago by andrsuh
  1

• Failing maven build

  #29 opened 2 years ago by Neliitsme
  1

• 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

  #7 opened 2 years ago by andrsuh
  0

• Create fair Spring Boot starter as a separate maven module and artifact

  #5 opened 2 years ago by andrsuh
  0

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

  #21 opened 2 years ago by andrsuh
  0

• Currently all the aggregates and events require to be registered. Use Reflections and make it registering automatically. Also we can introduce the property that defines which package should be scanned.

  #9 opened 2 years ago by andrsuh
  0

• Sagas. Research and implement.

  #20 opened 2 years ago by andrsuh
  0

• Update method should be able to return the new "updated" version of the aggregate state

  #18 opened 2 years ago by andrsuh
  0

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

  #13 opened 2 years ago by andrsuh
  1

• 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

  #17 opened 2 years ago by andrsuh
  0

• 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

  #12 opened 2 years ago by andrsuh
  0

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

  #11 opened 2 years ago by andrsuh
  0

• 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 (probably continuation) which should be handled properly.

  #10 opened 2 years ago by andrsuh
  0

• Implement idempotent streams subscriber

  #6 opened 2 years ago by andrsuh
  0

• Db operations for event sourcing should be suspend

  #4 opened 2 years ago by andrsuh
  0