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

"I am impressed with the tool’s latency. Also, the messages in ActiveMQ wait in a queue. The messages will start to move when the system reopens after getting stuck."
"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."
"The initial setup is straightforward and only takes a few minutes."
"I'm impressed, I think that Active MQ is great."
"ActiveMQ brings the most value to small applications because it will not cost you very much to complete."
"The most important feature is that it's best for JVM-related languages and JMS integration."
"ActiveMQ demonstrates excellent stability and sturdiness."
"We value ActiveMQ for its performance, throughput, and low latency, especially in handling large volumes of data and sequential management of topics."
"The performance of Redis is very fast."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"The ability to fetch and save data quickly is valuable."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The online interface is very fast and easy to use."
"The in-memory data makes it fast."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"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."
 

Cons

"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"It does not scale out well. It ends up being very complex if you have a lot of mirror queues."
"From the TPS point of view, it's like 100,000 transactions that need to be admitted from different devices and also from the different minor small systems. Those are best fit for Kafka. We have used it on the customer side, and we thought of giving a try to ActiveMQ, but we have to do a lot of performance tests and approval is required before we can use it for this scale."
"We need to enhance stability and improve the deployment optimization to fully leverage the platform's capabilities."
"The solution's stability needs improvement."
"The solution can improve the other protocols to equal the AMQ protocol they offer."
"This solution could improve by providing better documentation."
"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."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"Redis presents a single point of failure and lacks fault tolerance."
"For the PubSub feature, we had to create our own tools to monitor the events."
"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 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."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"Redis should have an option to operate without Docker on a local PC."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
 

Pricing and Cost Advice

"We are using the open-source version, so we have not looked at any pricing."
"The solution is less expensive than its competitors."
"I think the software is free."
"ActiveMQ is open source, so it is free to use."
"It’s open source, ergo free."
"I use open source with standard Apache licensing."
"There are no fees because it is open-source."
"We use the open-source version."
"Redis is an open-source solution. There are not any hidden fees."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"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.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
31%
Computer Software Company
11%
Manufacturing Company
8%
Government
6%
Financial Services Firm
25%
Computer Software Company
12%
Educational Organization
7%
Comms Service Provider
7%
 

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.
868,787 professionals have used our research since 2012.