Thanks Tim.
We're going to try a couple different solutions.
On Fri, Sep 27, 2019 at 1:13 AM Tim Bain wrote:
> Yes, if you're looking for competing consumer semantics but for each
> message to be consumed exactly once in each data center, then a network of
> brokers with a virtual topic atop th
Yes, if you're looking for competing consumer semantics but for each
message to be consumed exactly once in each data center, then a network of
brokers with a virtual topic atop the two queues would be my first thought
for how to do this. I've not personally done any bridging of virtual
destination
Hello Tim.
Thanks for taking the time for a response.
You are correct. The setup is being used to keep the 2 datacenters
completely in sync. It allows us to switch our reporting frontend to the
other datacenter at any time if we are having issues at the opposite
datacenter. The messages are co
William,
If I understand you correctly, you're using Camel to clone the message so
you get one per data center, and then using Camel to move the message from
the data center at which it was produced to the other one. And you're doing
this so that you can have all messages reach consumers in both d
We have the following configuration.
3 brokers in Datacenter A in a master/slave configuration using a shared
file system. 3 brokers in Datacenter B in a master/slave configuration
using a shared file system.
There are producers sending messages to topics at Datacenter A. There are
Camel routes r
