Try our new research platform with insights from 80,000+ expert users

ActiveMQ vs Redis comparison

 

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
5.7
Number of Reviews
23
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st), Vector Databases (4th)
 

Featured Reviews

Eyob Alemu - PeerSpot reviewer
Efficient data flow management with high performance and occasional stability improvements
For high traffic volumes where management time on ActiveMQ is minimal and where the rate of flow from the provider is slower than from the consumer, ActiveMQ offers the highest performance based on our experience. It has been efficient for data flow control between two endpoints, despite occasional unexpected glitches. I'd rate the solution eight out of ten.
Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.

Quotes from Members

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

Pros

"The initial setup and first deployment of ActiveMQ is fairly simple."
"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."
"There is a vibrant community, and it is one of the strongest points of this product. We always get answers to our problems. So, my experience with the community support has been good."
"Reliable message delivery and mirroring."
"ActiveMQ is very lightweight and quick."
"ActiveMQ demonstrates excellent stability and sturdiness."
"The main function I find valuable in ActiveMQ is facilitating message transfer within the client's internal network. ActiveMQ handles the message transfer from the internal network to the cloud. Regarding multi-protocols, we use different approaches based on client capabilities. Some clients connect for real-time data transfer, using database queries for periodic updates every ten minutes. We collect data from multiple clients, ensuring we get real-time sensor values where possible and periodic updates for others."
"The most valuable feature of this solution is the holding and forwarding."
"The performance of Redis is very fast."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The ability to fetch and save data quickly is valuable."
"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."
"Redis is a simple, powerful, and fast solution."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
"The online interface is very fast and easy to use."
"Redis is a simple service that does what it promises."
 

Cons

"We need to enhance stability and improve the deployment optimization to fully leverage the platform's capabilities."
"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."
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"The tool needs to improve its installation part which is lengthy. The product is already working on that aspect so that the complete installation gets completed within a month."
"I would like the tool to improve compliance and stability. We will encounter issues while using the central applications. In the solution's future releases, I want to control and set limitations for databases."
"There are some stability issues."
"AI capabilities require improvement in future updates."
"The solution's stability needs improvement."
"For the PubSub feature, we had to create our own tools to monitor the events."
"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."
"There is a lack of documentation on the scalability of the solution."
"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."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"If we use a lot of data, it will eventually cost us a lot."
"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."
"The solution's pricing for a local installation is very expensive."
 

Pricing and Cost Advice

"I use open source with standard Apache licensing."
"It’s open source, ergo free."
"We use the open-source version."
"ActiveMQ is open source, so it is free to use."
"The solution is less expensive than its competitors."
"There are no fees because it is open-source."
"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."
"We saw an ROI. It made the processing of our transactions faster."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is an open-source product."
"Redis is not an overpriced solution."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
865,140 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
33%
Computer Software Company
10%
Manufacturing Company
8%
Government
6%
Financial Services Firm
24%
Computer Software Company
13%
Educational Organization
7%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about ActiveMQ?
For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery.
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 do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
The disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters. The sync between the nodes is easier to implement with Couchbase, for e...
What is your primary use case for Redis?
Redis is used for a part of a booking engine for travel, specifically for the front part to get some sessions and information about the sessions. If a customer or user is using the sites in differe...
 

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 ActiveMQ vs. Redis and other solutions. Updated: July 2025.
865,140 professionals have used our research since 2012.