Likelihood to Recommend We used it in two cases, and it went pretty good with both. We used it for analytics and logging alongside event-based communication between different tech-stacks. One thing that users need to keep in mind is that it has a limited knowledgebase and will need a good understanding of Kafka to use it efficiently. So choose it carefully and when its needed
Read full review It is highly recommended that if you have microservices architecture and if you want to solve 2 phase commit issue, you should use RabbitMQ for communication between microservices. It is a quick and reliable mode of communication between microservices. It is also helpful if you want to implement a job and worker mechanism. You can push the jobs into RabbitMQ and that will be sent to the consumer. It is highly reliable so you won't miss any jobs and you can also implement a retry of jobs with the dead letter queue feature. It will be also helpful in time-consuming API. You can put time-consuming items into a queue so they will be processed later and your API will be quick.
Read full review Pros It is adaptive and helps us create more engaging experiences on our platforms. The Key metrics dashboard is rich with insights. Read full review 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. Read full review Cons Provide Capabilities to connect the Event Streams via REST Proxy. Schema Registry to handle Avro Formats. Provide Kafka Connect Sink & Source Connectors. Read full review 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. Read full review Usability The product was very user friendly and extremely easy to get started with. The documentation is excellent and the free tier makes it very easy to get started with without having to make deep or long term financial commitments.
Read full review RabbitMQ is very usable if you are a programmer or DevOps engineer. You can setup and configure a messaging system without any programmatic knowledge either through an admin console plugin or through a command-line interface. It's very easy to spin up additional consumers when volume is heavy and it's very easy to manage those consumers either through automated scripting or through their admin console. Because it's language agnostic it integrates with any system supporting AMQP.
Read full review Support Rating I met with the support team and they have deep technical and development understanding of the needs and the problems which IBM Event Streams addresses. If you are looking for a product backed by a highly technical support team then IBM Event Streams is probably the best choice. I was specifically impressed by the level of technical understanding my support team demonstrated.
Read full review RabbitMQ is more software than service so there's no real customer service to speak of unless you go with a provider such as CloudAMQP. So I'll just speak on CloudAMQP. Their customer support is only okay: they only do it over email. They frequently gloss over our support tickets and half answer them without delving deeply or investigating our issues. Their response times are pretty reasonable though.
Read full review Alternatives Considered In Event Streams, applications send data by creating a message and sending it to a topic. To receive messages, applications subscribe to a topic. High availability and reliability. Event Streams offers a highly available and reliable Apache Kafka service running on IBM Cloud. Event Streams. Event Streams stores three replicas of your data to ensure the highest level of resilience across three availability zones.
Read full review RabbitMQ has a few advantages over
Azure Service Bus 1) RMQ handles substantially larger files - ASB tops out at 100MB, we use RabbitMQfor files over 200MB 2) RabbitMQ can be easily setup on prem -
Azure Service Bus is cloud only 3) RabbitMQ exchanges are easier to configure over ASB subscriptions ASB has a few advantages too 1) Cloud based - just a few mouse clicks and you're up and running
Read full review Return on Investment In using downstreams, the minimal features and the rate of releases were slow, makes us feel that there's no upgrades and other than that there's poor marketing of the product. The adoption around the service is low, requires focused marketing. Lack of visibility into topic depth , Monitoring capabilities Read full review Earlier we had a problem with missing work items with our own implementation but later using RabbitMQ is solved a problem. Now our job processing mechanism is highly reliable. We also had a problem with scaling, processing 1k work items per second. RabbitMQ helped us to scale well with increasing work items. Read full review ScreenShots