TrustRadius: an HG Insights company

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

    Redis Software

    Score8.8 out of 10
    N/ARedis is an open source in-memory data structure server and NoSQL database.N/A
    Pricing
    RabbitMQRedis Software
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    RabbitMQRedis Software
    Free Trial
    NoYes
    Free/Freemium Version
    NoYes
    Premium Consulting/Integration Services
    NoYes
    Entry-level Setup FeeNo setup feeOptional
    Additional Details——
    More Pricing Information
    Community Pulse
    RabbitMQRedis Software
    Considered Both Products
    Open Source
    Chose RabbitMQ
    For basic use cases, SQS is way easy to deploy and maintain compared to RabbitMQ. RabbitMQ can cover a lot more use-cases but actually, we did not face specific scenarios that make it necessary to come back to RabbitMQ.
    Incentivized
    Redis
    Chose Redis Software
    UI isn't that great compared to the other competitors.
    The management of our memcached cluster was becoming pretty complicated as the application grew in size. Redis is a much better option compared to memcached.
    Redis is bit unreliable compared to the alternative RabbitMQ …
    Incentivized
    Key User Insights
    Would buy again
    91%
    Would buy again
    10 Answers
    100%
    Would buy again
    6 Answers
    Delivers good value for the price
    100%
    Delivers good value for the price
    11 Answers
    100%
    Delivers good value for the price
    6 Answers
    Happy with the feature set
    91%
    Happy with the feature set
    10 Answers
    100%
    Happy with the feature set
    6 Answers
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    7 Answers
    100%
    Lived up to sales and marketing promises
    6 Answers
    Implementation went as expected
    100%
    Implementation went as expected
    11 Answers
    100%
    Implementation went as expected
    6 Answers
    Best Alternatives
    RabbitMQRedis Software
    Small Businesses
    No answers on this topic
    No answers on this topic
    Medium-sized Companies
    Apache Kafka
    Score8.9 out of 10
    No answers on this topic
    Enterprises
    Apache Kafka
    Score8.9 out of 10
    No answers on this topic
    All AlternativesView all alternativesView all alternatives
    User Ratings
    RabbitMQRedis Software
    Likelihood to Recommend
    9.9
    (11 ratings)
    8.0
    (76 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    8.7
    (12 ratings)
    Usability
    8.0
    (1 ratings)
    9.0
    (6 ratings)
    Support Rating
    6.5
    (4 ratings)
    8.7
    (5 ratings)
    Implementation Rating
    -
    (0 ratings)
    7.3
    (1 ratings)
    User Testimonials
    RabbitMQRedis Software
    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
    Redis
    Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
    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
    Redis
    • Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
    • Reliable. With a proper multi-node configuration, it can handle failover instantly.
    • Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
    • Fast. We process tens of thousands of RPS and it doesn't skip a beat.
    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
    Redis
    • We had some difficulty scaling Redis without it becoming prohibitively expensive.
    • Redis has very simple search capabilities, which means its not suitable for all use cases.
    • Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
    Incentivized
    Read full review
    Likelihood to Renew
    Open Source
    No answers on this topic
    Redis
    We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
    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
    Redis
    It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
    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
    Redis
    The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
    Incentivized
    Read full review
    Implementation Rating
    Open Source
    No answers on this topic
    Redis
    Whitelisting of the AWS lambda functions.
    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
    Redis
    We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
    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
    Redis
    • Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
    • Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
    • Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
    Incentivized
    Read full review
    ScreenShots

    Redis Software Screenshots

    Screenshot of Database configurationScreenshot of Database metricsScreenshot of DatabasesScreenshot of NodesScreenshot of Alerts