Replicating IBM MQ with Amazon MQ - Amazon MQ
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Replicating IBM MQ with Amazon MQ

Amazon MQ provides a variety of broker configurations, various instance sizes for different workloads, and broker options such as single instance, single instance mesh, active/standby instance or active/standby mesh for high availabilty and message durability. To learn more about supported broker options, see Amazon MQ Broker Architecture.

In this section, we replicate the IBM MQ system shown in the previous section with Amazon MQ, while keeping the same configuration.

Amazon MQ manages the work involved in setting up an ActiveMQ message broker, from provisioning the infrastructure capacity (server instances and storage) to installing the broker software. Once your broker is up and running, Amazon MQ automates common administrative tasks such as patching the ActiveMQ software that power your brokers.

Note

If you wish to use a single region, you can simply deploy your Amazon MQ brokers in one region with the active/standby configuration. You can also optimize the performance of your Amazon MQ brokers by taking advantage of the Apache ActiveMQ optimization settings.

The following diagram illustrates Amazon MQ configured across two regions with a linear connection between two active/standby brokers:

For App 1 to communicate with App 2:

  1. Client applications can use a transport connector and put messages onto a Queue or publish to a Topic.

  2. Brokers connect to each other over a network connector either in one direction or both directions in cases where request-reply messaging is required.

  3. Queues and users can be created and managed in the Amazon Console. To learn more, see Amazon MQ Basic Elements.

Note

  • A transmit queue in IBM MQ is a local queue, except it is used to forward messages to a remote IBM MQ queue manager through a sender-receiver channel pair. In Amazon MQ, a transmit queue is not required. Once 2 brokers are connected using a network connector, they begin to share all queues/topics, and their data.

  • A remote queue in IBM MQ is a local impression of a remote queue available at a remote IBM MQ queue manager. For external applications, there is no difference between local or remote queues. In Amazon MQ, there is no remote queue mechanism and it is not required.

  • Sender or receiver channels in IBM MQ are used as network paths to connect 2 IBM MQ queue managers. In Amazon MQ, this functionality is implemented using network connectors.

  • Currently, Amazon MQ only supports JMS 1.1. Applications written for JMS 2.0 can be migrated to Amazon MQ using the Qpid JMS library, which uses AMQP instead of the default, higher-performing Openwire protocol. For more details, refer to the Amazon MQ workshop.