We performed a comparison between Apache Kafka and PubSub+ Event Broker 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 most valuable feature is the support for a high volume of data."
"Resiliency is great and also the fact that it handles different data formats."
"The most valuable feature is the documentation, which is good and clear."
"The most valuable feature is that it can handle high volume."
"There are numerous possibilities that can be explored. While it may be challenging to fully comprehend the potential advantages, one key aspect is the ability to establish a proper sequence of events rather than simply dealing with a jumbled group of occurrences. These events possess their own timestamps, even if they were not initially provided with one, and are arranged in a chronological order that allows for a clear understanding of the progression of the events."
"The ability to partition data on Kafka is valuable."
"All the features of Apache Kafka are valuable, I cannot single out one feature."
"The main advantage is increased reliability, particularly with regard to data and the speed with which messages are published to the other side."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"Going from something where we had outages and capacity issues constantly to a system that was able to scale with the massive market data and messaging spikes that happened during the initial stages of the COVID crisis in March, we were able to scale with 40 plus percent growth in our platform over the course of days."
"The way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"In my assessment of Solace against other products — as I was responsible for evaluating various products and bringing the right tool into companies in the past — I worked with multiple platforms like RabbitMQ, Confluent, Kafka, and various other tools in the market. But I found the event mesh capability to be a very interesting as well as fulfilling capability, towards what we want to achieve from a digital-integration-strategy point of view... It's distributed, yet it is intelligently connected. It can also span and I can plug and play any number of brokers into the event mesh, so it's a great deal. That's a differentiator."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"The most useful features has been the WAN optimization and probably the HybridEdge, which requires some third-party adapters or plugins. The idea that we can position Solace as a protocol-agnostic message transport fabric is key to our company having all manners of asynchronous messaging protocols from MQ, Kafka, JMS, etc. I really like the WAN optimization: Send once over a WAN, then distribute locally as many times as there are subscribers."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"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."
"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."
"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."
"Data pulling and restart ability need improving."
"The price for the enterprise version is quite high. It would be better to have a lower price."
"We cannot apply all of our security requirements because it is hard to upload them."
"One of the things I am mostly looking for is that once the message is picked up from Kafka, it should not be visible or able to be consumed by other applications, or something along those lines. That feature is not present, but it is not a limitation or anything of the sort; rather, it is a desirable feature. The next release should include a feature that prevents messages from being consumed by other applications once they are picked up by Kafka."
"The solution can improve by having automation for developers. We have done many manual calculations and it has been difficult but if it was automated it would be much better."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"The ease of management could be approved. The GUI is very good, but to configure and manage these devices programmatically in the software version is not easy. For example, if I would like to spin up a new software broker, then I could in theory use the API, but it would require a considerable amount of development effort to do so. There should be a tool, or something that Solace supports, that we could use for this, e.g., a platform like Terraform where we could use infrastructure as code to configure our source appliances."
"The deployment process is complex."
"One of the areas of improvement would be if we could tell the story a bit better about what an event mesh does or why an event mesh is foundational to a large enterprise that has a wide diversity of applications that are homegrown and a small number off the shelf."
"We've pointed out some things with the DMR piece, the event mesh, in edge cases where we could see a problem. Something like 99 percent of users wouldn't ever see this problem, but it has to do with if you get multiple bad clients sending data over a WAN, for example. That could then impact other clients."
"For improvements, I would suggest increasing the max payload size to a limit of 100MB or more. The current max payload size is limited to 5MB."
"The integrations could improve in PubSub+ Event Broker."
Apache Kafka is ranked 1st in Message Queue (MQ) Software with 78 reviews while PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews. Apache Kafka is rated 8.0, while PubSub+ Event Broker is rated 8.6. The top reviewer of Apache Kafka writes "Real-time processing and reliable for data integrity". On the other hand, the top reviewer of PubSub+ Event Broker writes "Event life cycle management changes the way a designer or architect will design a topic and discover what is available". Apache Kafka is most compared with IBM MQ, Amazon SQS, Red Hat AMQ, Anypoint MQ and VMware Tanzu Data Services, whereas PubSub+ Event Broker is most compared with IBM MQ, ActiveMQ, VMware Tanzu Data Services, Confluent and Amazon EventBridge. See our Apache Kafka vs. PubSub+ Event Broker 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.