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 processing power of Apache Kafka is good when you have requirements for high throughput and a large number of consumers."
"Scalability is very good."
"Deployment is speedy."
"Kafka, as compared with other messaging system options, is great for large scale message processing applications. It offers high throughput with built-in fault-tolerance and replication."
"The most valuable feature is the messaging function and reliability."
"All the features of Apache Kafka are valuable, I cannot single out one feature."
"Good horizontal scaling and design."
"The most important feature for me is the guaranteed delivery of messages from producers to consumers."
"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."
"When we went to add another installation in our private cloud, it was easy. We received support from Solace and the install was seamless with no issues."
"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 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."
"This solution reduces the latency to access changes in real-time and the effort required to onboard a new subscriber. It also reduces the maintenance of each of those interfaces because now the publisher and subscribers are decoupled. Event Broker handles all the communication and engagement. We can just push one update, then we don't have to know who is consuming it and what's happening to that publication downstream. It's all done by the broker, which is a huge benefit of using Event Broker."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"The most valuable feature of PubSub+ Event Broker is the scaling integration. Prior to using the solution, it was done manually with a file, and it can be done instantly live."
"Kafka is a nightmare to administer."
"The graphical user environment is currently lacking."
"The price for the enterprise version is quite high. It would be better to have a lower price."
"The model where you create the integration or the integration scenario needs improvement."
"Apache Kafka could improve data loss and compatibility with Spark."
"There are some latency problems with Kafka."
"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 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 deployment process is complex."
"We have requested to be able to get into the payload to do dynamic topic hierarchy building. A current workaround is using the message's header, where the business data can be put into this header and be used for a dynamic topic lookup. I want to see this in action when there are a couple of hundred cases live. E.g., how does it perform? From an administration perspective, is the ease of use there?"
"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 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 integrations could improve in PubSub+ Event Broker."
"The section on observability pertains to understanding the functioning of an event crash. Instead of focusing on how the crash occurs, attention is given to the observable aspects, such as a memory pipeline where one person pushes messages and another reads them. However, this pipeline often encounters issues, such as the reader being unavailable, causing the system to become stuck and preventing the messages from moving forward. This can lead to the pipeline being permanently stalled."
"If you create one event in the past, you cannot resend it."
"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."
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.