These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
TCStableis not that easy as this event has to be consumed by all
CRDTActors, right? But a
CRDTActoris an aggregate so a central emitter would have to route the event explicitly to each and every aggregate which does not seem to be feasible. So I guess an event would have to be emitted by the
CRDTActoritself. OTOH this would end up in one
TCStableevent per CRDT which also seems to introduce quite some overhead.
a CRDTActor is an aggregate so a central emitter would have to route the event explicitly to each and every aggregate which does not seem to be feasible
True, I had forgotten this. The CRDTManager should have to be an EventsourcedActor that creates CRDTActor on events, and use this events to maintain a set of their aggregate ids to use it as customAggregateId when the TCStable is persisted. It's seems pretty complex, if it feasible at all, and I don't know the cost involved in use large set of custom aggregate ids for delivery.
If you agree, I will implement a first version solving stability per CRDTActor (without persist TCStable) and share it with you when I'm done.