TrustRadius Insights
RabbitMQ has proven to be an invaluable tool for organizations grappling with communication challenges in a microservices architecture. …
Overview
What is RabbitMQ?
RabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more. RabbitMQ is available open source, however VMware also offers a range of commercial services for…
Recent Reviews
Reviewer Pros & Cons
Product Demos
Federated Message Queue Demo
YouTube
RabbitMQ Producer and Consumer Demo
YouTube
RabbitMQ demo
YouTube
Demo aplikasi RabbitMQ dan hubungan antara Message Broker dan RabbitMQ || Tugas 2 EAI
YouTube
RabbitMQ with MQTT plugin demo
YouTube
Demo: Spring Insight plugins for Spring Integration and RabbitMQ
YouTube
Product Details
- About
- Tech Details
- FAQs
What is RabbitMQ?
RabbitMQ Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Frequently Asked Questions
RabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more.
RabbitMQ is available open source, however VMware also offers a range of commercial services for RabbitMQ; these are available as part of the Pivotal App Suite.
Reviewers rate Support Rating highest, with a score of 6.5.
The most common users of RabbitMQ are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(39)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
RabbitMQ has proven to be an invaluable tool for organizations grappling with communication challenges in a microservices architecture. Users have successfully utilized RabbitMQ to address these problems by facilitating seamless communication between various microservices. Another common use case is employing RabbitMQ as a job processing mechanism, where work items are pushed into the RabbitMQ queue and processed based on topic. This feature has streamlined task distribution and improved efficiency in many organizations. Additionally, RabbitMQ has been integrated as a backbone for homegrown ESBs, enabling smooth routing and transaction movement between ESB endpoints. One of the standout features of RabbitMQ is its new quorum queues, which allow multiple queue consumers across a cluster of servers, resulting in virtually zero downtime during routine maintenance. This feature has proven invaluable to organizations seeking high availability and reliability in their messaging infrastructure. Furthermore, RabbitMQ has demonstrated its versatility by serving as an efficient messaging and queuing system between disconnected applications on different platforms, such as .Net Web Site and Linux Server. This capability has empowered organizations with diverse technology stacks to seamlessly communicate and exchange data between systems. Another noteworthy use case is the development of custom frameworks using RabbitMQ to distribute tasks and commands between microservices. This flexibility allows organizations to tailor the messaging system to their specific needs and effectively manage their microservice architecture. Moreover, RabbitMQ has found utility in managing users and projects within organizations, providing robust communication capabilities between teams. It has also been used as a medium for communication between nano-services, enabling seamless coordination in complex distributed systems. In several instances, RabbitMQ has emerged as the go-to solution for managing outgoing emails, text messages, and faxes from various systems across entire businesses. This centralized approach streamlines communications processes and enhances overall efficiency. Additionally, RabbitMQ serves as a reliable service bus for communication across microservice APIs, ensuring fault tolerance and improving system resilience. Notably, it has been successfully deployed for monitoring SMS service delivery platforms, offering valuable insights into delivery counts and performance. Iterable, a prominent user of RabbitMQ, relies on the messaging system to queue incoming messages and schedule work for later execution. This use case highlights the versatility of RabbitMQ in managing workflows and optimizing message processing. Overall, RabbitMQ stands as an old yet mature and maintained queuing system, enabling organizations to develop rich applications with advanced architectures. It seamlessly integrates with other software products, such as Ellucian Banner and Genesys Pulse, to facilitate integration and asynchronous messaging. Through its wide range of use cases, RabbitMQ has proven to be a reliable and versatile solution for organizations seeking efficient communication and task distribution. Its robust messaging capabilities have made it an ideal choice for managing outgoing emails, text messages, and faxes across various systems within businesses. Moreover, RabbitMQ serves as a reliable service bus for communication across microservice APIs, providing built-in fault tolerance and enhancing system resilience. The software has also found utility in monitoring SMS service delivery platforms, offering valuable insights into delivery counts and performance. Companies like Iterable rely on RabbitMQ to queue incoming messages and schedule work for later execution, demonstrating its versatility in managing workflows and optimizing message processing. Overall, RabbitMQ is an old yet mature queuing system that empowers organizations to develop rich applications with advanced architectures. By seamlessly integrating with other software products such as Ellucian Banner and Genesys Pulse, RabbitMQ enables integration and asynchronous messaging for enhanced efficiency and scalability.
Efficient and Effective Routing: Several users have praised the routing capability of RabbitMQ, stating that it efficiently and effectively routes work items based on topic. This feature allows for easy processing by subscribers of the RabbitMQ queue.
High Scalability: Many reviewers appreciate the scalability of RabbitMQ, especially when handling a large number of work items. They mention that RabbitMQ scales well with a cluster approach, making it highly reliable for executing work items.
Easy-to-Use Web UI: The web UI of RabbitMQ is widely appreciated by users for its ease-of-use. Customers find its intuitive interface convenient for quickly performing tasks without any hassle.
Communication Breakdowns: Some users have experienced frequent communication breakdowns when using RabbitMQ, especially during time-consuming work items or when errors occur. These breakdowns can cause the RabbitMQ channel to break, resulting in disruptions and potential data loss.
Installation Complexity: Installing RabbitMQ on Windows can be a tricky process, particularly when it involves setting up clustering. Users have reported difficulties and challenges in properly configuring the cluster setup and ensuring seamless communication between nodes.
Lack of Observability: One major drawback that users commonly face with RabbitMQ is the lack of built-in observability features. Many users find it inconvenient to perform essential tasks such as checking messages in a queue or listing all queues without relying on additional tools or configurations. This limits their ability to effectively monitor and manage their messaging system.
Users have made several recommendations for RabbitMQ as a message broker service. These are the three most common recommendations:
-
Utilize the advanced routing feature: Users have praised RabbitMQ for its advanced routing capabilities. This feature allows for complex message routing and enables efficient communication between different components in a project.
-
Benefit from easy integration: Many users have found RabbitMQ to be straightforward to integrate into their projects. The tool offers various client libraries and supports multiple programming languages, making it adaptable to different development environments.
-
Leverage scalability and reliability: Reviewers often highlight RabbitMQ's ability to handle large message volumes and maintain high levels of reliability. The tool's support for clustering and persistence ensures that messages are delivered reliably, even in demanding environments.
Overall, users recommend using RabbitMQ as a message broker service due to its advanced routing, ease of integration, and scalability/reliability features.
Attribute Ratings
Reviews
(1-11 of 11)Companies can't remove reviews or game the system. Here's why
August 11, 2023
Worth investing in
We use RabbitMQ in conjunction with our own homegrown ESB. RabbitMQ acts as a backbone to our ESB for routing and enabling us to move transactions from one ESB endpoint to another. The new quorum queues enable have multiple queue consumers across a cluster of RabbitMQ servers meaning we have virtually zero downtime during routine maintenance.
- High performance queues
- Exchanges (routing)
- Easy to use web UI
- Easy deployment
- Installing on Windows has some quirks especially with clustering
- When disk is full, it stops transactions which can be problematic to recover from
- .net SDK doesn't always recover nicely from network drops
We are using microservices architecture so communication between services is the most important part. RabbitMQ helped us to solve the communication problem between microservices. Another use case is we have our own job processing mechanism, RabbitMQ helped us to push work items in the RabbitMQ queue and process it based on topic.
- Routing of work items based on topic. We can push work items in a RabbitMQ queue which is topic based and those will be processed by subscriber of that queue.
- Scaling with so many work items. RabbitMQ scales well with cluster approach that will help us when we have so many work items.
- It tracks work items status, if worker crashes then the same will be passed on to other worker. This way it will be highly reliable that work item must be executed sooner or later.
- It breaks communication if we don't acknowledge early. In some cases our work items are time consuming that will take a time and in that scenario we are getting errors that RabbitMQ broke the channel. It will be good if RabbitMQ provides two acknowledgements, one is for that it has been received at client side and second ack is client is completed the processing part.
July 24, 2022
RabbitMQ got the Job done in a simple scenario
We used RabbitMQ at a few clients as an efficient messaging and Queuing System. In particular, we were looking for a way to use messaging between disconnected apps on different platforms. The Producer App was in the .Net Web Site and the consumer was a service running on a Linux Server.
- Queuing
- Simple SetUp
- Easy to integrate with
- A bit complicated to take full advantage of its features.
- Dashboard could be improved.
July 19, 2022
Free carrots for RabbitMQ
We started to use RabbitMQ because it was a prerequisite for using Genesys Pulse in Realtime mode. From that, it was an interesting alternative to Queuing we used like MSMQ to deal with asynchronous messaging between 2 components.
- Several libraries in many languages our customers use.
- Mirroring to deal with failures.
- Scalability to deal with high rate in producer.
- More "Rabbit" plugins
- UI for monitoring
December 20, 2021
A RabbitMQ user in a microservices environment
RabbitMQ is our service bus and is how we perform communication across our microservice APIs. We have about a dozen or so microservices which all make use of RabbitMQ. It's extremely integral to our systems and the fact that you can send a message with built-in fault tolerance is pretty incredible when you think about it.
- Messaging
- Fault Tolerance
- Ease of Integration
- The admin dashboard could use some improvements
- Can be difficult to administer the bus
August 03, 2021
RabbitMQ, a nice tool that may be too complex
RabbitMQ was the queuing system we previously used before shifting to AWS SQS. The product is "old" yet very mature and maintained. This software helped us to create rich applications with advanced architectures. It is very easy to use and can scale very well to cover a large range of use cases.
- Awesome documentation
- Undoubtedly Efficient
- Can cover a large range of use cases
- Can be hard to maintained
- Difficult to monitor
June 02, 2021
Powerful platform, honest and well documented.
Score 9 out of 10
Vetted Review
Verified User
We used Pivotal RabbitMQ in order to develop our own framework. We have a custom architecture to distribute task and commands between our micro services. The effect of RabbitMQ reached all organization as we developed Administration backend UIs for all departments.
The organization managed users and the project using RabbitMQ.
Previously, in other organization we used it as medium to communicate nano-services following a similar pattern as previously described.
- Document the internal processes of Pivotal RabbitMQ so you fully understand what can and cannot do.
- Concurrency and resource utilization.
- Handling dead letter queues and giving flexibility to create your own dead letter systems.
- AMQL 0.9.1 is extremely flexible.
- Shovels are quite raw to use.
- More AMQP extensions like the publisher confirmation for not requiring so many queues.
- Easy AMQP entities configuration changes on production.
October 29, 2019
Solid messaging system
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.
October 16, 2019
RabbitMQ software review
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
October 04, 2019
Outdated but still reliable
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.
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.
August 06, 2019
High Performance Distributed Messaging
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