TrustRadius: an HG Insights company

RabbitMQ vs. Red Hat JBoss Enterprise Application Platform

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    RabbitMQ

    Score9.5 out of 10
    N/ARabbitMQ, 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.N/A

    Red Hat JBoss EAP

    Score8.5 out of 10
    N/AN/AN/A
    Pricing
    RabbitMQRed Hat JBoss EAP
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    RabbitMQRed Hat JBoss EAP
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Community Pulse
    RabbitMQRed Hat JBoss EAP
    Considered Both Products
    Open Source
    No answer on this topic
    Red Hat
    No answer on this topic
    Key User Insights
    Would buy again
    91%
    Would buy again
    10 Answers
    No answers on this topic
    Delivers good value for the price
    100%
    Delivers good value for the price
    11 Answers
    No answers on this topic
    Happy with the feature set
    91%
    Happy with the feature set
    10 Answers
    No answers on this topic
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    7 Answers
    No answers on this topic
    Implementation went as expected
    100%
    Implementation went as expected
    11 Answers
    No answers on this topic
    Features
    RabbitMQRed Hat JBoss EAP
    Application Servers
    Comparison of Application Servers features of RabbitMQ and Red Hat JBoss Enterprise Application Platform
    Feature
    RabbitMQ
    -
    Ratings
    Red Hat JBoss Enterprise Application Platform
    6.8
    9 Ratings
    15% below category average
    IDE support00 Ratings6.09 Ratings
    Security management00 Ratings7.09 Ratings
    Administration and management00 Ratings8.09 Ratings
    Application server performance00 Ratings8.09 Ratings
    Installation00 Ratings5.09 Ratings
    Open-source standards compliance00 Ratings7.09 Ratings
    Best Alternatives
    RabbitMQRed Hat JBoss EAP
    Small Businesses
    No answers on this topic
    NGINX
    Score9.1 out of 10
    Medium-sized Companies
    Apache Kafka
    Score8.9 out of 10
    Oracle WebLogic Server
    Score7.3 out of 10
    Enterprises
    Apache Kafka
    Score8.9 out of 10
    NGINX
    Score9.1 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    RabbitMQRed Hat JBoss EAP
    Likelihood to Recommend
    9.9
    (11 ratings)
    8.1
    (8 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    5.0
    (1 ratings)
    Usability
    8.0
    (1 ratings)
    8.5
    (3 ratings)
    Performance
    -
    (0 ratings)
    8.7
    (3 ratings)
    Support Rating
    6.5
    (4 ratings)
    5.2
    (2 ratings)
    Ease of integration
    -
    (0 ratings)
    8.5
    (3 ratings)
    User Testimonials
    RabbitMQRed Hat JBoss EAP
    Likelihood to Recommend
    Open Source
    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.
    Incentivized
    Read full review
    Red Hat
    JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.
    Incentivized
    Read full review
    Pros
    Open Source
    • 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.
    Incentivized
    Read full review
    Red Hat
    • MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
    • Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
    • Supports deployment in on-premise, virtual and hybrid cloud environments.
    Incentivized
    Read full review
    Cons
    Open Source
    • 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.
    Incentivized
    Read full review
    Red Hat
    • Difficult to replicate configuration outside of a container environment
    • Still requires quite a bit of knowledge of the CLI
    • Integration with deployment tools requires CLI knowledge
    Incentivized
    Read full review
    Likelihood to Renew
    Open Source
    No answers on this topic
    Red Hat
    We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop
    Incentivized
    Read full review
    Usability
    Open Source
    RabbitMQ is very easy to configure for all supported languages (Python, Java, etc.). I have personally used it on Raspberry Pi devices via a Flask Python API as well as in Java applications. I was able to learn it quickly and now have full mastery of it. I highly recommend it for any IoT project.
    Incentivized
    Read full review
    Red Hat
    JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.
    Incentivized
    Read full review
    Performance
    Open Source
    No answers on this topic
    Red Hat
    JBoss EAP is lightweight and doesn't really consumes much physical resources. It's high performing and suites well for high transaction Java enterprise applications. The out of box performance settings are not really great and you will have to configure the settings to suite your environment to leverage it's full benefits.
    Incentivized
    Read full review
    Support Rating
    Open Source
    I gave it a 10 but we do not have a support contract with any company for RabbitMQ so there is no official support in that regard. However, there is a community and questions asked on StackOverflow or any other major question and answer site will usually get a response.
    Incentivized
    Read full review
    Red Hat
    Fast response.
    Incentivized
    Read full review
    Alternatives Considered
    Open Source
    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
    Incentivized
    Read full review
    Red Hat
    We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.
    Incentivized
    Read full review
    Return on Investment
    Open Source
    • Positive: we don't need to keep way too many backend machines around to deal with bursts because RabbitMQ can absorb and buffer bursts long enough to let an understaffed set of backend services to catch up on processing. Hard to put a number to it but we probably save $5k a month having fewer machines around.
    • Negative: we've got many angry customers due to queues suddenly disappearing and dropping our messages when we try to publish to them afterward. Ideally, RabbitMQ should warn the user when queues expire due to inactivity but it doesn't, and due to our own bugs we've lost a lot of customer data as a result.
    • Positive: makes decoupling the web and API services from the deeper backend services easier by providing queues as an interface. This allowed us to split up our teams and have them develop independently of each other, speeding up software development.
    Incentivized
    Read full review
    Red Hat
    • Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
    • Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.
    Incentivized
    Read full review
    ScreenShots