These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
Hey there :)
I’m currently trying to create an EventsourcedProcessor that reads an event from event log A and writes a newly created event to event log B. I want the newly created event to be equipped with an aggregate ID. Unfortunately, AFAICS the event that will be sent to event log B can only contain the same “customDestinationAggregateIds” as the original event from event log A (which btw. doesn’t have and IMO shouldn’t have an aggregate ID).
Am I right here that the API does not permit to realise such a scenario? Is this intended?
Event deletion is not implemented yet for Cassandra but is planned. Assuming the feature already exists, I'd store events of anonymous users in a separate log that is then cleaned up based on application defined criteria (retention time or whatever ...). I cannot make any promises ATM when we start working on that feature ... (it is a bit more involved as deletions in replicated event logs should be causally consistent).
@krasserm: A few more questions regarding deletion and some other things:
ReplicationEndpoint. Looking at the source it seems to be possible to send a
Deletemsg the EventLog Actor as well. We actually only have one location right now where local event logs seem to be enough or is it best practice to still create a
ReplicationEndpoint? We have multiple deployed nodes which will access the same log but as I understood there is no explicit replication needed for that since both Nodes would access the same local event log?!
Some generic questions: