ylorph

Command can be rejected by the system, events can not be rejected by the system

Yes , when the first edition is out of print, the second one will be yellow

+1 for the lightning icon

I'm referring to what greg says => state is a left fold of the events list

https://twitter.com/hryz3/status/1295485020317130759 (comments by Ian Cooper & Anton Hryzodu Article by Oliver Libutzki https://dev.to/olibutzki/why-event-sourcing-is-a-microservice-anti-pattern-3mcj

The Reference https://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf

well it a way to prevent concurrent append to a stream , as well as keeping it's projectected state in memory. ( if only 1 actor has ownership of appending...

This might be interesting too https://collection-json.github.io/

It's the "Behave in synchronous manner" that's difficult for me. It's higly dependent on the requirements, expectations, limitations of the client . with the chaining DoCommand(cmd).DoQuery (query) what if the...

Other things that might be of interrest; * client IP address for client-initiated actions