I've been reading up here on PersistentActor, and I think I get how that
works to perform commands and write the result to an event store. I also
think I understand that PersistentViews can subscribe to a PersistentActor
and receive notification of each event stored for that PersistentActor
On Wednesday, July 15, 2015 at 10:43:55 AM UTC-7, Giovanni Alberto
Caporaletti wrote:
Hi Magnus.
a question concerning your pull model: if the updates are idempotent, why
would I need a parent aggregate? Can't the views directly populate the read
store?
This is a great question, and