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), Managed NoSQL Databases (9th), 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 ability to store the failed events for some time is valuable."
"The initial setup and first deployment of ActiveMQ is fairly simple."
"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."
"ActiveMQ demonstrates excellent stability and sturdiness."
"The most valuable feature of this solution is the holding and forwarding."
"ActiveMQ brings the most value to small applications because it will not cost you very much to complete."
"I appreciate many features including queue, topic, durable topic, and selectors. I also value a different support for different protocols such as MQTT and AMQP. It has full support for EIP, REST, Message Groups, UDP, and TCP."
"I'm impressed, I think that Active MQ is great."
"Redis is a simple service that does what it promises."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
"It is particularly efficient for cloud-based storage and operations."
"The product offers fast access to my database."
"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."
"Redis acts as an in-memory search tool that improves the speed of operations."
"I use Redis mostly to cache repeated data that is required."
 

Cons

"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."
"It would be great if it is included as part of the solution, as Kafka is doing. Even though the use case of Kafka is different, If something like data extraction is possible, or if we can experiment with partition tolerance and other such things, that will be great."
"There are some stability issues."
"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."
"This solution could improve by providing better documentation."
"One potential area would be the complexity of the initial setup."
"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."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"For the PubSub feature, we had to create our own tools to monitor the events."
"If we use a lot of data, it will eventually cost us a lot."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"Redis presents a single point of failure and lacks fault tolerance."
"It's actually quite expensive."
"Redis should have an option to operate without Docker on a local PC."
"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."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Financial Services Firm
32%
Computer Software Company
10%
Manufacturing Company
8%
Government
6%
Financial Services Firm
24%
Computer Software Company
12%
Educational Organization
8%
Comms Service Provider
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 Business11
Midsize Enterprise3
Large Enterprise8
 

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: September 2025.
867,497 professionals have used our research since 2012.