Have you heard of this https://github.com/Comcast/cmb? Maybe it's along the
path of what you're looking for.
On 22 February 2014 22:33, Jonathan Haddad j...@jonhaddad.com wrote:
Upfront TLDR: We want to do stuff (reindex documents, bust cache) when
changed data from DC1 shows up in DC2.
Hi Jonathan--
First, best wishes for success with your platform.
Frankly, I think the architecture you described is only going to cause
you major trouble. I'm left wondering why you don't either use something
like XMPP (of which several implementations can handle this kind of
federated scenario)
Thanks for the input Todd. I've considered a few of the options you've
listed. I've ruled out redis because it's not really built for multi DC.
I've got nothing against XMPP, or SQS. However, they introduce race
conditions as well as all sorts of edge cases (missed messages, for
instance).
Upfront TLDR: We want to do stuff (reindex documents, bust cache) when
changed data from DC1 shows up in DC2.
Full Story:
We're planning on adding data centers throughout the US. Our platform is
used for business communications. Each DC currently utilizes elastic
search and redis. A message
Upfront TLDR: We want to do stuff (reindex documents, bust cache) when
changed data from DC1 shows up in DC2.
Full Story:
We're planning on adding data centers throughout the US. Our platform is
used for business communications. Each DC currently utilizes elastic
search and redis. A message
