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

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

"ActiveMQ is very lightweight and quick."
"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."
"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."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"Reliable message delivery and mirroring."
"Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"It provides the best support services."
"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 ability to fetch and save data quickly is valuable."
"It is particularly efficient for cloud-based storage and operations."
"The product offers fast access to my database."
"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 in-memory data makes it fast."
"Redis is a simple service that does what it promises."
"The performance of Redis is very fast."
"Redis is good for distributed caching management."
 

Cons

"The solution's stability needs improvement."
"It does not scale out well. It ends up being very complex if you have a lot of mirror queues."
"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."
"We need to enhance stability and improve the deployment optimization to fully leverage the platform's capabilities."
"Needs to focus on a certain facet and be good at it, instead of handling support for most of the available message brokers."
"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."
"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."
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"It's actually quite 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."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"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."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"Redis should have an option to operate without Docker on a local PC."
"Redis presents a single point of failure and lacks fault tolerance."
"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

"The solution is less expensive than its competitors."
"I use open source with standard Apache licensing."
"I think the software is free."
"We use the open-source version."
"We are using the open-source version, so we have not looked at any pricing."
"There are no fees because it is open-source."
"ActiveMQ is open source, so it is free to use."
"It’s open source, ergo free."
"Redis is an open-source product."
"The tool is open-source. There are no additional costs."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"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.
849,686 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?
There are a few areas where Redis could improve. The pub-sub capabilities could be optimized to handle network sessions better, as there are challenges with maintaining sessions between clients and...
What is your primary use case for Redis?
We use Redis ( /products/redis-reviews ) for several purposes, including ranking, counting, saving, sharing, caching, and setting time-to-live notifications. These functionalities are employed acro...
 

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: April 2025.
849,686 professionals have used our research since 2012.