No more typing reviews! Try our Samantha, our new voice AI agent.

ActiveMQ vs Redis comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

ActiveMQ
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
28
Ranking in other categories
Message Queue (MQ) Software (2nd)
Redis
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
NoSQL Databases (4th), Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (5th), AI Software Development (9th)
 

Featured Reviews

MD
Software Engineer III at a financial services firm with 10,001+ employees
Integration capabilities enhance message handling without human interaction
With ActiveMQ there should be more options. If you work with other technologies, for example, Java, there are many options. We can integrate the way we want ActiveMQ. We can create partitions and clusters, but AP is not providing such options currently. It only provides time, request response timing, the number of requests that need to be handled, and protocol types. The configuration needs to be broadened inside AP to perform in a better way. Sometimes issues arise in production with ActiveMQ due to the number of requests. For example, if you have configured one thousand requests at a time and it receives one thousand and one messages at a time, it breaks. The configuration aspect is tricky. When configurations are proper, ActiveMQ almost has zero errors.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Depending on the problem, AMQ resolved nearly everything."
"ActiveMQ demonstrates excellent stability and sturdiness."
"One of the most important features of ActiveMQ is the ability to set up a network of brokers, and the ability to forward the message to another broker in the network, where there is a demand for messages from a consumer."
"It is cost effective and is a much cheaper solution compared to Weblogic or IBM MQ."
"ActiveMQ brings the most value to small applications because it will not cost you very much to complete."
"ActiveMQ is a good solution; it is low cost, high performance, and scalable."
"The ability to store the failed events for some time is valuable."
"Message broadcasting: There could be a use case sending the same message to all consumers. So as a producer, I broadcast the message to a topic. Then, whichever consumers are subscribed to the topic can consume the same message."
"Redis is a simple service that does what it promises."
"It is particularly efficient for cloud-based storage and operations."
"The product offers fast access to my database."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"The online interface is very fast and easy to use."
"Redis acts as an in-memory search tool that improves the speed of operations, allowing for quicker data retrieval and enhancing the performance of applications."
"The ability to fetch and save data quickly is valuable."
 

Cons

"There is need for more protocols and maybe they should provide documentation on the internet as well."
"The clustering for sure needs improvement. When we were using it, the only thing available was an active/passive relationship that had to be maintained via shared file storage. That model includes a single point of failure in that storage medium."
"We ran into various stability problems with our implementations over the years."
"It does not scale out well. It ends up being very complex if you have a lot of mirror queues."
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"The UI. It's both a good thing and a bad thing. The UI is too simple. Sometimes you wanna see the messages coming to the queue, and you have to refresh the dashboard, the console of the product."
"Sometimes issues arise in production with ActiveMQ due to the number of requests. For example, if you have configured one thousand requests at a time and it receives one thousand and one messages at a time, it breaks."
"Because this is an open-source project, there is no support. We don't have any help or anything like that."
"The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"It's actually quite expensive."
"If we use a lot of data, it will eventually cost us a lot."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."
 

Pricing and Cost Advice

"We use the open-source version."
"There are no fees because it is open-source."
"The solution is less expensive than its competitors."
"We are using the open-source version, so we have not looked at any pricing."
"The tool's pricing is reasonable and competitive compared to other solutions."
"I think the software is free."
"ActiveMQ is open source, so it is free to use."
"It’s open source, ergo free."
"Redis is an open-source product."
"We saw an ROI. It made the processing of our transactions faster."
"The tool is open-source. There are no additional costs."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
920,929 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
10%
Computer Software Company
8%
Comms Service Provider
7%
Financial Services Firm
21%
Comms Service Provider
8%
Computer Software Company
7%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise17
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with ActiveMQ?
Pricing is something to consider with ActiveMQ, though cloud pricing is not costly and depends upon the compute selection. Focusing on AI is essential nowadays. AI capabilities require improvement ...
What is your primary use case for ActiveMQ?
In my current organization, I'm only working with ActiveMQ. I previously worked with IBM WebSphere MQ.
What advice do you have for others considering ActiveMQ?
We have not deployed ActiveMQ's flexible clustering as that requirement is not present for us. We only use active-passive configuration. On a scale of one to ten, I rate ActiveMQ a ten out of ten.
What needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

Comparisons

 

Also Known As

AMQ
Redis Enterprise
 

Overview

 

Sample Customers

University of Washington, Daugherty Systems, CSC, STG Technologies, Inc. 
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about IBM, Apache, Amazon Web Services (AWS) and others in Message Queue (MQ) Software. Updated: October 2026.
920,929 professionals have used our research since 2012.