@Ryan Tanner Thanks for the info. Regarding Kafka, I would love to use
kafka replication to solve this problem. However, the purpose of the system
I'm building is to bootstrap the replication of kafka, by launching mirror
maker processes. So there is a bit of a chicken and egg problem there.
I'm not particularly surprised by this, but I'm curious: do you know if
anyone has done any serious work on Akka "meta-clusters" for situations
like this? For example, while it's certainly at least a few years off, I
should *probably* eventually distribute my Cluster Sharding geographically,
I agree with Ryan that it's generally not recommended.
I would like to add that the cluster membership and distributed data will
work pretty fine across DC thanks to their gossip based protocols, but
there are other tools, such as cluster sharding, that are not a good fit
for it.
Cluster downing
Akka is generally not recommended for spanning data centers.
I would consider the cluster client, though personally I'd probably choose
Kafka for this role, with separate clusters in each DC. IME cross-DC
communication is generally a scenario where you really want to make sure
messages are
