eventflow
eventflow copied to clipboard
svalaskevicius
cqrs+es in scala
local lock per aggregate id, block until it frees up -- is it needed? would it be helpful at all?
Cqrs as package name might better be eventflow. As recommended by @Akii
Automating commands based on previous events
- time started / time running - total number of commands processed - total number of events received from db - total number of events actually consumed by projections -...
projections can emit events that other projections / sagas depend on
the system should handle the upgrade path when there are some events for the original version stored in the DB, but aggregate definition needs to change support new domain knowledge.