1

I am evaluating ActiveMQ Artemis as a potential replacement for SonicMQ. In Sonic, we have the ability for a client producing a message to determine the final broker destination.

Simplified example:

  • We have a broker in each of two regions: Europe and Americas.
  • Each broker holds an identically named set of queues (e.g.: europe::q1 and americas::q1)
  • Clients are restricted to connecting only to their local broker but have the ability to define the destination queue as being managed by a remote broker.

For instance, a client in Europe may post a message to:

  • "q1": Destination is europe::q1
  • "americas::q1": Destination is the queue named "q1" in Americas:
    • The Europe broker accepts the message before pushing it to the Americas broker.

If I understand the Artemis documentation, this behaviour may be configured on a permanent basis via Queue Federation.

Will Artemis allow for the final destination broker / queue to be determined on a per-message basis?

Justin Bertram
  • 29,372
  • 4
  • 21
  • 43
Cosmittus
  • 637
  • 6
  • 19

1 Answers1

1

Among other things, ActiveMQ Artemis supports "federation" between brokers which can automatically transfer messages from one broker to another. If you have a broker in two different regions it would be relatively trivial to create a "local" set of addresses & queues and a "remote" set of addresses and queues such that messages sent to the "local" resources would stay on that broker and messages sent to the "remote" resources would be automatically transferred to a broker in another region.

Technically speaking, the original producer of the message doesn't have exclusive control of where the message goes because it operates independently of the federation configuration on the broker. The producer simply sends messages to a particular destination on the local broker and then the federation configuration decides where the message goes after that.

Likewise, the final destination of the message isn't determined on a "per message" basis as if each message was individually inspected and the final destination is then based on some specific property of the message. Rather the message is just sent to a specific destination and then the broker's federation configuration decides where the message goes after that.

In any event, ActiveMQ Artemis should be able to support your use-case. It has a very flexible and powerful address model and a broad suite of features for moving messages between brokers.

Justin Bertram
  • 29,372
  • 4
  • 21
  • 43