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 initial setup is straightforward and only takes a few minutes."
"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."
"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."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"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."
"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."
"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."
"The in-memory data makes it fast."
"The solution is fast, provides good performance, and is not too expensive."
"The online interface is very fast and easy to use."
"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."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Redis is good for distributed caching management."
 

Cons

"Distributed message processing would be a nice addition."
"The solution can improve the other protocols to equal the AMQ protocol they offer."
"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."
"One potential area would be the complexity of the initial setup."
"We need to enhance stability and improve the deployment optimization to fully leverage the platform's capabilities."
"I would rate the stability a five out of ten because sometimes it gets stuck, and we have to restart it. We"
"It does not scale out well. It ends up being very complex if you have a lot of mirror queues."
"For additional functionality, I suggest making it easier to install and monitor the queues, topics, broker status, publisher status, and consumer status. Improved monitoring tools would help avoid needing to manually access the server for monitoring purposes."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"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."
"Redis should have an option to operate without Docker on a local PC."
"Redis presents a single point of failure and lacks fault tolerance."
"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."
"It's actually quite expensive."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
 

Pricing and Cost Advice

"I think the software is free."
"We use the open-source version."
"The solution is less expensive than its competitors."
"ActiveMQ is open source, so it is free to use."
"It’s open source, ergo free."
"I use open source with standard Apache licensing."
"We are using the open-source version, so we have not looked at any pricing."
"There are no fees because it is open-source."
"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 not an overpriced solution."
"Redis is an open-source product."
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.