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
7.8
Reviews Sentiment
7.1
Number of Reviews
26
Ranking in other categories
Message Queue (MQ) Software (2nd)
Redis
Average Rating
8.8
Reviews Sentiment
8.1
Number of Reviews
21
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st), Vector Databases (5th)
 

Featured Reviews

Prashant-Sharma - PeerSpot reviewer
Allows for asynchronous communication, enabling services to operate independently but issues with stability
The feature of ActiveMQ which I feel is good is its ability to have DLP, the later queues. If something goes wrong with the platform, it retries. Even if it fails, it goes to DLP, and later we can rescan the same event for processing. The ability to store the failed events for some time is valuable.
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

"Reliable message delivery and mirroring."
"It provides the best support services."
"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."
"We value ActiveMQ for its performance, throughput, and low latency, especially in handling large volumes of data and sequential management of topics."
"The most important feature is that it's best for JVM-related languages and JMS integration."
"The initial setup is straightforward and only takes a few minutes."
"For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery."
"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."
"The in-memory data makes it fast."
"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 provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"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 use Redis efficiently."
"The product offers fast access to my database."
"I use Redis mostly to cache repeated data that is required."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"Redis is a simple service that does what it promises."
 

Cons

"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."
"The solution's stability needs improvement."
"Distributed message processing would be a nice addition."
"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."
"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."
"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."
"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."
"I would rate the stability a five out of ten because sometimes it gets stuck, and we have to restart it. We"
"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."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"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."
"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."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"The solution's pricing for a local installation is very expensive."
"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."
 

Pricing and Cost Advice

"I use open source with standard Apache licensing."
"There are no fees because it is open-source."
"The tool's pricing is reasonable and competitive compared to other solutions."
"The solution is less expensive than its competitors."
"I think the software is free."
"ActiveMQ is open source, so it is free to use."
"We use the open-source version."
"It’s open source, ergo free."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"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.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
34%
Computer Software Company
11%
Manufacturing Company
9%
Government
7%
Financial Services Firm
22%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
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?
We need to address the non-deterministic load issues. Sometimes, ActiveMQ either restarts automatically or goes into ActiveMQ mode, causing interruptions. We need to enhance stability and improve t...
What is your primary use case for ActiveMQ?
We have a digital ID platform that uses various services running on Kafka. There are two main endpoints where services interact with external services. These include an automatic biometric service ...
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?
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. Additionally, better documentation is neede...
What is your primary use case for Redis?
I use Redis as a tool in building projects, specifically for in-memory caching. My backend API uses Redis to cache information retrieved from the database.
 

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: January 2025.
838,713 professionals have used our research since 2012.