Sarunas Valaskevicius
Sarunas Valaskevicius
also can optimise out then one read query from db to catch up from db
# Saga - saga tracks events same way as projections - they're also allowed to talk to the external world - saga supports storing "position pointer", to be restored back...
based on this, add a test for snapshotting - snapshotted aggregate should read less events from db on consecutive actions
... or can projection definition to be simplified and focus be put on composability?
I think now that projection should never emit events - aggregates and sagas should be used instead. Will leave the ticket to discuss how to compose projections
:+1: exactly what I thought as well :) initially I created this ticket following geteventstore.com but I think staying in pure aggregate/projection/saga definition is better for now
Hmm at this point I think it's good to separate domain events and UI notifications, which can be done in either pull or push manner :)
Hmm so for this purpose we could add a notification param for a projection, that is pinged when projection processes some data. App layer can then use this to update...
Yepp. Agreed :)
I think I have the same issue.. Vim+rls on nixos cannot go to rust src definitions, but can go to imported crates... As I'm new to rust, please can you...