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 of Apache Kafka is the clustering which is very easy to scale and we have multiple servers all over our platforms. It has been useful for stability and performance."
"The solution is very easy to set up."
"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."
"When comparing it with other messaging and integration platforms, this is one of the best rated."
"It's an open-source product, which means it doesn't cost us anything to use it."
"The open-source version is relatively straightforward to set up and only takes a few minutes."
"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."
"We get amazing throughput. We don't get any delay."
"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."
"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."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"More adapters for connecting to different systems need to be available."
"Kafka does not provide control over the message queue, so we do not know whether we are experiencing lost or duplicate messages."
"In the next release, I would like for there to be some authorization and HTL security."
"There are some latency problems with Kafka."
"Stability of the API and the technical support could be improved."
"I suggest using cloud services because the solution is expensive if you are using it on-premises."
"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."
"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."
"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."
"Some of the feature's gaps with some of the open-source vendors have been closed in a lot of ways. Being more agile and addressing those earlier could be an area for improvement."
"The deployment process is complex."
"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."
"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."
"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 licensing and the cost are the major pitfalls."
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.