Hi Kunal-
I expect you’ll get a wide range of responses here =). ActiveMQ has two
brokers, and they do similar things but it essentially comes down to who is the
best fit for supporting your organizations’ ActiveMQ infrastructure?
I take exception to Justin’s comments here — ActiveMQ Classic ha
Development on Classic has slowed considerably since focus has shifted to
Artemis. Most of the folks who've contributed the most code to Classic
historically have either left the project or moved over to Artemis. The
Artemis repo has almost 100 more total committers and almost as many
commits as th
Hi Kunal,
What kind of workload is your broker cluster designed for? I don't think
there is an easy answer here as these two brokers have different sets of
features implemented. It really depends on your requirements on supported
features and performance. For instance, if your application requires
Thanks Justin.
I am planning to use Amazon MQ (only supports classic) as a central broker
and Artemis as satellite brokers with the assumption that artemis is a more
supported product and classic is treated as legacy with regards to
development and support.
Firstly, Is my assumption correct?
We ar
Just to clarify...ActiveMQ Classic doesn't support the Core protocol so
that is why you can't use a Core bridge to integrate.
Justin
On Thu, Oct 3, 2024 at 8:29 AM Justin Bertram wrote:
> Yes. You can bridge messages from Artemis to Classic and vice versa.
> However, you can't use a Core bridg
Yes. You can bridge messages from Artemis to Classic and vice versa.
However, you can't use a Core bridge to do it. Core bridges, as the name
suggests, use the Core protocol. A Core bridge can't use the AMQP protocol.
I recommend Camel since it's mature, powerful, and ubiquitous. You can set
up Ca
