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."For example, when you want to send a message to inform all your clients about a new feature, you can publish that message to a single topic in Apache Kafka. This allows all clients subscribed to that topic to receive the message. On the other hand, if you need to send billing information to a specific customer, you can publish that message on a topic dedicated to that customer. This message can then be sent as an SMS to the customer, allowing them to view it on their mobile device."
"As a software developer, I have found Apache Kafka's support to be the most valuable...The solution is easy to integrate with any of our systems."
"Robust and delivers messages quickly."
"The valuable features are the group community and support."
"One of the most valuable features I have found is Kafka Connect."
"The most valuable feature of Apache Kafka is Kafka Connect."
"When comparing it with other messaging and integration platforms, this is one of the best rated."
"The high availability is valuable. It is robust, and we can rely on it for a huge amount of data."
"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."
"We've built a lot of products into it and it's been quite easy to feed market data onto the systems and put entitlements and controls around that. That was a big win for us when we were consolidating our platforms down. Trying to have one event bus, one messaging bus, for the whole globe, and consolidate everything over time, has been key for us. We've been able to do that through one API, even if it's across the different languages."
"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."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"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."
"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."
"An area for improvement would be growth."
"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."
"It's not possible to substitute IBM MQ with Apache Kafka because the JMS part is not very stable."
"Too much dependency on the zookeeper and leader selection is still the bottleneck for Kafka implementation."
"Apache Kafka can improve by providing a UI for monitoring. There are third-party tools that can do it, but it would be nice if it was already embedded within Apache Kafka."
"Pulsar gives more scalability to an even grouping, but Apache Kafka is used more if you want to send something in a time series-based. If this does not matter to you then Pulsar could be more customizable. Apache Kafka is nothing but a streaming system with local storage."
"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."
"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."
"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."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"The deployment process is complex."
"The licensing and the cost are the major pitfalls."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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."
"If you create one event in the past, you cannot resend it."
"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?"
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.