Replicated event sourcing across two Akka Clusters #29575
Labels
discuss
Tickets that need some discussion before proceeding. Not decided if it's a good idea.
t:replicated-event-sourcing
Replicated active event sourcing
This may just work if we turn off the event publishing with cross reading but at least we should test and document.
I think this may end up being quite a common setup. For example, when the DCs have different Kubernetes clusters. In this scenario pods from the clusters may not be addressable and any communication may need to go via ingress. This won't work for Akka Cluster as we need peer to peer communication.
The text was updated successfully, but these errors were encountered: