Dapr: Add Event-Sourced Persistent Actors

[jasoncarreira]

Support Event Sourcing and CQRS for persistent actors. The actor would maintain the current state in-memory and only store the events in an event store. The event stream could feed read-side state stores (CQRS) as well. This should also support event translation to a stream of domain events (different from the persistent entity events) over pub-sub which other services / actors could subscribe to.

An interesting option is to implement the spec from Cloudstate.io for ES/CQRS and CRDTs.

[yaron2]

Support Event Sourcing and CQRS for persistent actors. The actor would maintain the current state in-memory and only store the events in an event store. The event stream could feed read-side state stores (CQRS) as well. This should also support event translation to a stream of domain events (different from the persistent entity events) over pub-sub which other services / actors could subscribe to.

An interesting option is to implement the spec from Cloudstate.io for ES/CQRS and CRDTs.

We're looking into Event Sourcing and CRDTs, also with CloudState.
Will post updates here and relevant questions.

[perokvist]

Hi,

Interesting. I think that supporting storing events in streams through "State/StateClient" would be a great starting point to build on top of. And the input binding for possible subscription support.

I posted and issue on the topic of "event store" support #907 with "State" and CosmosDB as an example.

[amanbha]

@perokvist Could you provide a more detailed proposal?