IronMQ vs Red Hat AMQ Broker

IronMQ is a persistent message queue for communication between services and components in distributed applications. It supports push and pull queues, long polling, error queues, alerts, and triggers, as well as dead-letter queues and ordering within each queue. Delivery is described as best-effort and one-time, a behavior application teams should account for in message handling. Its HTTPS and REST-based APIs support HTTP/REST, Amazon SQS, and OpenStack Marconi protocols. During an outage, queues can automatically point to alternative availability zones without code changes. Deployment options include shared, dedicated, and on-premise environments. Documentation lists client libraries for Go, Ruby,.NET, Java, PHP, Python, Node, and Rust, plus community-supported Apache Camel and Clojure libraries. Iron.io says OAuth and SSL protect data in transit, and recommends client-side encryption for especially sensitive payloads at rest. The free Basic plan includes 100K API requests per month, limited queues, and a 64k message size limit. Entry costs $399 a month; a full-feature 14-day trial is offered for non-dedicated clusters.

Red Hat AMQ Broker has no write-up on Specifiction yet; its figures are above.