Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replicated event sourcing across two Akka Clusters #29575

Open
chbatey opened this issue Sep 9, 2020 · 2 comments
Open

Replicated event sourcing across two Akka Clusters #29575

chbatey opened this issue Sep 9, 2020 · 2 comments
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

Comments

@chbatey
Copy link
Member

chbatey commented Sep 9, 2020

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.

@chbatey chbatey added t:replicated-event-sourcing Replicated active event sourcing discuss Tickets that need some discussion before proceeding. Not decided if it's a good idea. labels Sep 9, 2020
@patriknw
Copy link
Member

patriknw commented Sep 9, 2020

Sounds good to try this. So the db connection across two different Kubernetes cluster will work?

@chbatey
Copy link
Member Author

chbatey commented Sep 9, 2020

That would be a requirement. The database may or not be in the other k8s cluster. I think this is an easier requirement to satisfy then interpod communication across k8s clusters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants