RabbitMQ

About RabbitMQ

Once an application grows past a handful of services talking to each other directly, message-oriented middleware stops being optional. Intuz’s RabbitMQ AMI puts the open-source message broker on Amazon EC2 with Apache pre-installed in the paid tier, implementing the Advanced Message Queuing Protocol with a plug-in architecture that also supports STOMP and other messaging protocols.

RabbitMQ’s flexible routing means messages can be directed to the right queue based on rules you define, rather than every consumer having to filter through every message, and the built-in tracing support means when something in your messaging layer misbehaves, you can actually see what happened instead of guessing from application logs alone.

Because this runs as a self-hosted instance rather than a managed queue service, your team controls throughput, retention, and scaling directly, which matters for teams running microservices architectures where message volume can spike unpredictably around specific events or batch jobs.

Password recovery and snapshot management scripts are included, so the operational basics are handled at the AMI level rather than left to whoever set up the instance to remember.

If RabbitMQ is one piece of a broader move toward decoupled, service-based architecture, it’s worth considering the full DevOps picture rather than just the messaging layer in isolation. If you’re looking for help with that, you can check out DevOps consulting and outsourcing services for that broader infrastructure and architecture work.

Key Features of RabbitMQ:

• It supports messaging over a variety of messaging protocols
• It offers tracing support to let you know what’s going on if your messaging system is misbehaving
• It has Password Recovery and Snapshot Management Scripts
• It supports flexible routing before they arrive at the queues

RabbitMQ Paid Stack

Intuz RabbitMQ Stack comes with a paid version which has apache2 and scripts which make it easy for you to use RabbitMQ.