guzzolm / eventlite Goto Github PK

If stance A changes the stream state while stance B is still processing a command, this state will be lost when B persists its stream state (B will replace stream state without knowing what A changed).

For the same reason, B will persist an event without knowing the event that A persisted.

This will cause data inconsistency.

Implement a way to replay the dispatch of events/commits done between a specific date.
This may be useful when using Event Sourcing with CQRS to feed read models

Allow the persistence (and publish) of Headers for events and/or Commits

While adding the following settings:

• cache
• snapshot
• Collections prefix (to distinguish aggregates).

Distributed or InMemory (handling concurrency and retrying when changes from other instances are detected when saving the Commit)

Core source code should only have main logic implementations and public interfaces. Database specific implementations should be in a separated project.

conceito de undispatched/dispatched commits (isto é importante para o proprio conceito de event sourcing. Se tá commited, temos de garantir que foi dispatched).

• identificar metodos para aplicação de eventos no carregamento do agregado e não por reflection. Muito à imagem da programação funcional, usando o conceito de as funções serem "Higher-order citizens" e poderem ser utilizadas e passadas por parametro/em variaveis.