Christian Posta — Software Blog

Become the best you can be at your profession. If you've stopped learning, you've given up.

Deploying JBoss A-MQ for High Availability scenarios

JBoss A-MQ  is based on Apache ActiveMQ. It’s lightweight, has excellent performance, and can be configured to fit a variety of use cases.

One of those use cases, and a requirement that you’ll find in most enterprises, is being able to have a messaging backbone that can withstand unplanned faults, planned outages, and other disaster scenarios. Scott Cranton and Jack Britton will be giving a webinar tomorrow on how to deploy and configure JBoss A-MQ to be highly available (HA) and give lots of good tips and tricks for complex scenarios, cloud deployments, and using Fuse Fabric.

The top companies in banking, e-commerce, retail, and health care, and others all use ActiveMQ and/or JBoss A-MQ. If you’re interested in learning more about deployment in the enterprise, make sure to catch Scott and Jack’s webinar!

3 Responses to “Deploying JBoss A-MQ for High Availability scenarios”

  • Mitch says:

    Couple questions…

    1. Is Apollo ready for a prime time? In other words, would it be remiss to do a new implementation of a message broker using using ActiveMQ instead of Apollo?
    2. What is the preferred way to publish/consume messages from apollo? The application code that publishes and consumes messages will be written in coldfusion. There are already some examples that come packaged with coldfusion that show you how to publish/consume from ActiveMQ but those are from 2007.

    Thanks.

    • admin says:

      Mitch,

      I would say Apollo has some good community penetration and that a couple of large organizations are putting it through the ringer and it’s been fairly stable. The question would really be around production support, and at the moment Apollo isn’t ‘officially’ supported (*yet!!!*). ActiveMQ 5.x is tried and true and has production support.

      So apollo supports 4 protocols: STOMP, Openwire (ActiveMQ 5.x clients), AMQP, and MQTT.

      STOMP over websockets might be your best bet for a browser-based client, but for traditional coldfusion on the server side, you’re best bet is probably STOMP over tcp…. STOMP is a very simple protocol, and should be easy to implement if no existing coldfusion client exists (but check first…)

      • Mitch says:

        Hopefully, by the time my company is ready to implement a message broker it will be supported. Unfortunately, there is no stomp implementation written in coldfusion so I will be writing that. Thanks for the feedback.


Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>