CloudAMQP vs Hutch: What are the differences?
Developers describe CloudAMQP as "RabbitMQ as a Service". Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms. On the other hand, Hutch is detailed as "Inter-Service Communication with RabbitMQ". Hutch is a Ruby library for enabling asynchronous inter-service communication in a service-oriented architecture, using RabbitMQ.
CloudAMQP and Hutch can be primarily classified as "Message Queue" tools.
Some of the features offered by CloudAMQP are:
- Support - 24/7 support, via email, chat and phone.
- Real time metrics and alarms - Get notified in advanced when your queues are growing faster than you're consuming them, when you're servers are over loaded etc. and take action before it becomes a problem.
- Auto-healing - Our monitoring systems automatically detects and fixes a lot of problems such as kernel bugs, auto-restarts, RabbitMQ/Erlang version upgrades etc.
On the other hand, Hutch provides the following key features:
- 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
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.