We performed a comparison between Apache Kafka and Aurea CX Messenger 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."The processing power of Apache Kafka is good when you have requirements for high throughput and a large number of consumers."
"We appreciate the ability to persistently and quickly write data, as well as the flexibility to customize it for multiple customers. Additionally, we like the ability to retain data within Apache Kafka and use features, such as time travel to access past customer data. The connection with other systems, such as Apache Kafka and IBM DB2."
"The most valuable feature is the support for a high volume of data."
"The ability to partition data on Kafka is valuable."
"The stream processing is a very valuable aspect of the solution for us."
"Apache Kafka is an open-source solution that can be used for messaging or event processing."
"I like the performance and reliability of Kafka. I needed a data streaming buffer that could handle thousands of messages per second with at least one processing point for an analytics pipeline. Kafka fits this requirement very well."
"Apache Kafka has good integration capabilities and has plenty of adapters in its ecosystem if you want to build something. There are adapters for many platforms, such as Java, Azure, and Microsoft's ecosystem. Other solutions, such as Pulsar have fewer adapters available."
"The features that I have found most valuable are that it is very easy to develop. Most of it is graphical, but we also have the option to add any custom call that you need."
"SDM: User-friendly tool which allows for a seamless approach to performing hotfixes, if required."
"The Messenger Broker is a really good feature."
"The solution is highly scalable, this is very important for us. It can handle a lot of messages."
"ESB: Provides all kind of possibilities to resolve business needs. A lot of ready to use services plus custom Java services. I used a lot of them all."
"The solution offers excellent stability."
"We cannot apply all of our security requirements because it is hard to upload them."
"The price for the enterprise version is quite high. It would be better to have a lower price."
"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."
"We struggled a bit with the built-in data transformations because it was a challenge to get them up and running the way we wanted."
"Kafka 2.0 has been released for over a month, and I wanted to try out the new features. However, the configuration is a little bit complicated: Kafka Broker, Kafka Manager, ZooKeeper Servers, etc."
"would like to see real-time event-based consumption of messages rather than the traditional way through a loop. The traditional messaging system works by listing and looping with a small wait to check to see what the messages are. A push system is where you have something that is ready to receive a message and when the message comes in and hits the partition, it goes straight to the consumer versus the consumer having to pull. I believe this consumer approach is something they are working on and may come in an upcoming release. However, that is message consumption versus message listening."
"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."
"As an open-source project, Kafka is still fairly young and has not yet built out the stability and features that other open-source projects have acquired over the many years. If done correctly, Kafka can also take over the stream-processing space that technologies such as Apache Storm cover."
"Aurea CX Messenger could improve by making better use of the new APIs"
"I don't know if the last version has the cloud option, but maybe that could be good. That could be something that is included."
"The improvement is that it should be on the cloud and use web services."
"The solution needs to improve support for new, more recent protocols on the API."
"You should not hurry with upgrades without testing the whole product completely."
"It should include/add more services with the product as per market demand. It should include custom Java services developed by any organization or provide a platform where users/developers can share ideas/custom services, etc."
Apache Kafka is ranked 1st in Message Queue (MQ) Software with 78 reviews while Aurea CX Messenger is ranked 10th in Message Queue (MQ) Software with 7 reviews. Apache Kafka is rated 8.0, while Aurea CX Messenger is rated 9.0. The top reviewer of Apache Kafka writes "Real-time processing and reliable for data integrity". On the other hand, the top reviewer of Aurea CX Messenger writes "Lightweight and efficient solution". Apache Kafka is most compared with IBM MQ, Amazon SQS, Red Hat AMQ, Anypoint MQ and PubSub+ Event Broker, whereas Aurea CX Messenger is most compared with Mule ESB, IBM MQ, TIBCO Enterprise Message Service and WSO2 Enterprise Integrator. See our Apache Kafka vs. Aurea CX Messenger 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.