|Amazon Releases Managed Message Broker Service for ActiveMQ|
|Written by Kay Ewbank|
|Tuesday, 05 December 2017|
Amazon has released Amazon MQ, a managed message broker service for Apache ActiveMQ, the open-source message broker that supports queues and topics, durable and non-durable subscriptions, push-based and poll-based messaging, and filtering, providing another option for administering and maintaining ActiveMQ.
Amazon has its own message queue software, Amazon SQS, but Apache ActiveMQ is preferred by many organizations. Amazon says that their customers who are using open-source message brokers say the main problem lies in their setup and on-going maintenance, with many spending over 10 hours of staff time a week on maintenance.
The tasks handled by Amazon MQ include responsibility for broker provisioning, patching, failure detection and recovery for high availability, and message durability.
You get access to the ActiveMQ console, and to APIs and protocols for messaging, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket. This means that if you have applications that use any of these standards and want to move to Amazon MQ, you can just move the code across unchanged.
You can create a single-instance Amazon MQ broker for development and testing, or an active/standby pair that spans Availability Zones, with automatic failover. Either way, you get data replication across AZs and a pay-as-you-go model for the broker instance and message storage.
The service is charged on pay as you go for broker instance and storage usage. There's no upfront payment or minimum fee. The AWS Free Tier includes up to 750 hours of a single-instance mq.t2.micro broker and up to 1GB of storage per month for one year. After that, billing is based on instance-hours and message storage, plus charges Internet data transfer if the broker is accessed from outside of AWS.
Amazon MQ is now available in the US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), and Asia Pacific (Sydney) regions.
or email your comment to: firstname.lastname@example.org
|Last Updated ( Tuesday, 05 December 2017 )|