Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud.
AWS offering for a managed message broker service for Apache ActiveMQ. Message brokers allow different software systems–often using different programming languages, and on different platforms–to communicate and exchange information.
Amazon MQ also supports RabbitMQ, a popular open-source message broker. Migrate your existing RabbitMQ message brokers to AWS without having to rewrite code.
Amazon MQ reduces your operational load by managing the provisioning, setup, and maintenance of ActiveMQ, a popular open-source message broker. Connecting your current applications to Amazon MQ is easy because it uses industry-standard APIs and protocols for messaging, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket. Using standards means that in most cases, there’s no need to rewrite any messaging code when you migrate to AWS.
Amazon MQ Broker:
We can create message broker according to our requirements. A broker can be a single-instance broker or active/standby broker.
Single Instance Broker contains one broker in one availability It communicates with the application and AWS storage location. It can be used for development and testing.
Active/Standby Broker contains two brokers in two different availability zones for high availability. It will communicate with the application and shared storage location. It can be used for automatic failover. For both modes, Amazon MQ provides data replication across AZs.
Benefits of Amazon MQ:
⦁ Application Integration:
Provides a way to integrate applications with different languages and different operating systems to communicate with each other.
No need for availability of producers or consumers at the same time. Provides queue to manage any number of requests at any point in time.
Allows one application to fire a message and continue with other tasks instead of waiting for a response.
Since queue lies between the application and communication is carried through the queue, failure of one system will not affect other application.
⦁ Cost Reduction:
Need to pay only for storage and broker instance as you use.
Amazon MQ Features
Amazon MQ uses industry-standard APIs and protocols for messaging, including Java Message Service (JMS), .NET Message Service (NMS), AMQP, STOMP, MQTT, OpenWire, and WebSocket.
Amazon MQ manages administrative tasks such as hardware provisioning, broker setup, software upgrades, and failure detection and recovery.
Amazon MQ stores your messages redundantly across multiple Availability Zones (AZs).
AWS MQ supports both single-instance brokers, suitable for evaluation and testing, and active/standby brokers for high availability in production. In the event of a failure of the broker, or even a full AZ outage, AWS MQ automatically fails over to the standby broker.
Active MQ messaging features:
Active MQ provides all the standard JMS features including:
⦁ point-to-point (message queues),
⦁ publish-subscribe (topics),
⦁ persistent and non-persistent modes,
⦁ JMS transactions,
⦁ and distributed (XA) transactions.
ActiveMQ also supports more complex patterns such as:
⦁ composite destinations (producers can send the same message to multiple destinations)
⦁ virtual destinations (publishers broadcast messages via a topic to a pool of receivers subscribing through queues)
ActiveMQ preserves the order of messages sent by a single producer to all consumers on a topic.
ActiveMQ supports message groups, which enable multiple consumers on a queue to process messages within a group in first-in, first-out (FIFO) order.
ActiveMQ also supports message redelivery and dead letter queues when a message cannot be delivered to its destination.
Amazon MQ Limitations
The AWS MQ provides 200 GB limited storage.
The API limits of Bucket Size is 100 per refill rate(/s) is 15.
The Amazon MQ accepts only Apache Kahana DB data storage. The LevelDB and JDBC are not supported.