RabbitMQ Reviews

10 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.0 out of 100

Do you work for this company? Manage this listing

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-4 of 4)

Patrick lampatt | TrustRadius Reviewer
October 15, 2019

RabbitMQ software review

Score 8 out of 10
Vetted Review
Verified User
Review Source
We have been using RabbitMQ in the IT department. We used it to monitor our SMS service delivery platform. To monitor the delivery counts, number of successful deliveries, failed delivery and also be able to monitor the performance of the SMS platform, as in [to see] if everything is working as expected.
  • Ability to give accurate performance results
  • Ability to interpret the systems data to a more simple readable format
  • Able to give graphical as well tabular analysis
  • Reliable - doesn't fail in its performance
  • More simplified, some aspects of it is a little technical though
Was most suitable whenever we wanted to know the successful delivery rate of our SMS platform.
Read Patrick lampatt's full review
Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Review Source
We at Iterable use RabbitMQ for two key features: (1) keeping a queue of all the incoming messages that need to be processed with some semblance of order (2) scheduling work to be done later.

The reason we need to keep a queue is that when our traffic spikes, we can have up 1 million messages coming in that need to be processed in some form or fashion. To expect the backend service to support that is crazy. Instead, we dump them into RabbitMQ to give our backend service time to process them. As for scheduling work, the use case is to give our customers control over when they want some form of work to be done. What we do is we store their work request into a RabbitMQ delay queue with a set expiration. When it expires, it expires into the normal queues where our backend service will process them.
  • What RabbitMQ does well is what it's advertised to do. It is good at providing lots of high volume, high availability queue. We've seen it handle upwards of 10 million messages in its queues, spread out over 200 queues before its publish/consume rates dipped. So yeah, it can definitely handle a lot of messages and a lot of queues. Depending on the size of the machine RabbitMQ is running on, I'm sure it can handle more.
  • Decent number of plugins! Want a plugin that gives you an interface to view all the queues and see their publish/consume rates? Yes, there's one for that. Want a plugin to "shovel" messages from one queue to another in an emergency? Check. Want a plugin that does extra logging for all the messages received? Got you covered!
  • Lots of configuration possibilities. We've tuned over 100 settings over the past year to get the performance and reliability just right. This could be a downside though--it's pretty confusing and some settings were hard to understand.
  • So why did I only give it a 5? Well, there is almost no observability out of the box. Want to see what messages are in a queue? You have to take messages out and re-enqueue them, breaking the order and risking message loss. What to list all the queues? You have to install a janky plugin that only works half the time and takes 5 seconds to refresh.
  • Delay queue expiration can cause RabbitMQ to grind to a halt. We've seen that when delay queues have over 1 million messages, they expire in an explosion! Or rather, in an ice-age. RabbitMQ tries to dump all the messages of an expired delay queue at once and it causes memory usage and CPU usage to spike and suddenly RabbitMQ stops accepting new messages into its other queues.
If you are looking for a message broker, RabbitMQ is pretty good. Its API lets you create tons of queues on demand and publish to all of them at once, while you can have 10+ consumers on each queue. It also does a good job of absorbing bursts of traffic. We've seen our queues get backed up to 3 million messages with no problem.

In the modern era of GDPR, you may run into problems with keeping messages encrypted out of the box in-flight and at-rest with RabbitMQ. Not saying it's impossible, but it's tough to set up and you have to pay a high overload.
Read this authenticated review
Anonymous | TrustRadius Reviewer
October 29, 2019

Solid messaging system

Score 9 out of 10
Vetted Review
Verified User
Review Source
RabbitMQ is used in conjunction with Ellucian Banner software, specifically Ellucian Ethos Integration product and Banner Events Publisher.
  • Easy to install.
  • Open source, so there is no software cost.
  • JSON compliant.
  • Support for SSL/TLS.
  • Failover RabbitMQ cluster for high traffic environments.
  • The documentation needs improvement in explaining how to configure the above-mentioned features.
RabbitMQ is flexible and has many potential usages. It is good for capturing data changes on the database and posting messages in the RabbitMQ queue - centralized auditing system. It is also good for developing a centralized login system.
Read this authenticated review
Christopher Maggiulli | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We currently use RabbitMQ to manage a majority of our outgoing emails, text messages, and faxes from a variety of different systems across the entire business. RabbitMQ sends outgoing notifications by brokering messages from producer (the source system) to consumer (the destination endpoint). For faxing our MQ instance takes in a message, generates a binary PDF file and drops it on an ActiveFax server (running on Windows 2012). For email notifications, we integrate of office 365 and for SMS we use a cloud-base provider. We a system to manage and store outgoing templates which are used during the message brokering process to send the correct notification template
  • High Performance
  • Integrates well with Spring
  • Easy Setup
  • Not a lot of tooling
  • Hard to get into the internals
  • Not incorporated in many enterprise systems
RabbitMQ is well suited to send asynchronous messages across distributed systems. We currently use it for outgoing notifications but also use it for image processing, batch processing, streaming, and other purposes. For example, we also use RabbitMQ in conjunction with Apache Camel to poll a file system for technical design files, parse those files, then fan the containing information into several different systems. Additionally, we use RabbitMQ for any long performing services (usually requested by a user from a browser) that do not require immediate feedback.
Read Christopher Maggiulli's full review

About RabbitMQ

RabbitMQ, an open source message broker, is now part of Pivotal Software, and supports message queue, multiple messaging protocols, and more.
Categories:  Message Queue

RabbitMQ Technical Details

Operating Systems: Unspecified
Mobile Application:No