Hutch vs IronMQ: What are the differences?

Hutch: Inter-Service Communication with RabbitMQ. Hutch is a Ruby library for enabling asynchronous inter-service communication in a service-oriented architecture, using RabbitMQ; IronMQ: Message Queue for any deployment. An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

Hutch and IronMQ can be categorized as "Message Queue" tools.

Some of the features offered by Hutch are:

• A simple way to define consumers (queues are automatically created and bound to the exchange with the appropriate binding keys)
• An executable and CLI for running consumers (akin to rake resque:work)
• Automatic setup of the central exchange

On the other hand, IronMQ provides the following key features:

• Instant High Availability- Runs on top cloud infrastructures and uses multiple high-availability data centers. Uses reliable datastores for message durability and persistence.
• Easy to Use- IronMQ is super easy to use. Simply connect directly to the API endpoints and you're ready to create and use queues. There are also client libraries available in any language you want – Ruby, Python, PHP, Java, .NET, Go, Node.JS, and more
• Scalable / High Performance- Built using high-performance languages designed for concurrency and runs on industrial-strength clouds. Push messages and stream data at will without worrying about memory limits or adding more servers.

Hutch is an open source tool with 712 GitHub stars and 103 GitHub forks. Here's a link to Hutch's open source repository on GitHub.