We performed a comparison between Apache Kafka and Redis based on real PeerSpot user reviews.
Find out in this report how the two Message Queue (MQ) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Apache Kafka is an open-source solution that can be used for messaging or event processing."
"I like Kafka's flexibility, stability, reliability, and robustness."
"The high availability is valuable. It is robust, and we can rely on it for a huge amount of data."
"One of the most valuable features I have found is Kafka Connect."
"The most valuable feature is that it can handle high volume."
"Apache Kafka is actually a distributed commit log. That is different than most messaging and queuing systems before it."
"Excellent speeds for publishing messages faster."
"It is a stable solution...A lot of my experience indicates that Apache Kafka is scalable."
"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."
"The ability to fetch and save data quickly is valuable."
"The product offers fast access to my database."
"The in-memory data makes it fast."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"Redis is a simple, powerful, and fast solution."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"I would like them to reduce the learning curve around the creation of brokers and topics. They also need to improve on the concept of the partitions."
"The manageability should be improved. There are lots of things we need to manage and it should have a function that enables us to manage them all cohesively."
"In the next release, I would like for there to be some authorization and HTL security."
"The third party is not very stable and sometimes you have problems with this component. There are some developments in newer versions and we're about to try them out, but I'm not sure if it closes the gap."
"Apache Kafka could improve data loss and compatibility with Spark."
"The management overhead is more compared to the messaging system. There are challenges here and there. Like for long usage, it requires restarts and nodes from time to time."
"The management tool could be improved."
"There have been some challenges with monitoring Apache Kafka, as there are currently only a few production-grade solutions available, which are all under enterprise license and therefore not easily accessible. The speaker has not had access to any of these solutions and has instead relied on tools, such as Dynatrace, which do not provide sufficient insight into the Apache Kafka system. While there are other tools available, they do not offer the same level of real-time data as enterprise solutions."
"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."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"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."
"There is a lack of documentation on the scalability of the solution."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS 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."
Apache Kafka is ranked 1st in Message Queue (MQ) Software with 78 reviews while Redis is ranked 7th in Database as a Service with 11 reviews. Apache Kafka is rated 8.0, while Redis is rated 8.4. The top reviewer of Apache Kafka writes "Real-time processing and reliable for data integrity". On the other hand, the top reviewer of Redis writes "Enables efficient caching and helps users fetch and save data quickly". Apache Kafka is most compared with IBM MQ, Amazon SQS, Red Hat AMQ, Anypoint MQ and Memphis, whereas Redis is most compared with Google Cloud Memorystore, Amazon SQS, Chroma, ActiveMQ and Pinecone. See our Apache Kafka vs. Redis report.
See our list of best Message Queue (MQ) Software vendors.
We monitor all Message Queue (MQ) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
