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."Kafka allows you to handle huge amounts of data and classify it into different categories. If you have huge amounts of data, Kafka is a very good solution for data classification."
"The stability is very nice. We currently manage 50 million events daily."
"Apache Kafka is an open-source solution that can be used for messaging or event processing."
"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."
"Kafka provides us with a way to store the data used for analytics. That's the big selling point. There's very good log management."
"The most valuable feature of Apache Kafka is its versatility. It can solve many use cases or can be a part of many use cases. Its fundamental value of it is in the real-time processing capability."
"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."
"Its availability is brilliant."
"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 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."
"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."
"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."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"Kafka does not provide control over the message queue, so we do not know whether we are experiencing lost or duplicate messages."
"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."
"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."
"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."
"Data pulling and restart ability need improving."
"Maintaining and configuring Apache Kafka can be challenging, especially when you want to fine-tune its behavior."
"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."
"The price for the enterprise version is quite high. It would be better to have a lower price."
"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."
"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."
"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."
"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."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"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 product should allow third-party agents to be installed. Currently, it is quite proprietary."
Apache Kafka is ranked 1st in Message Queue (MQ) Software with 76 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 "Great access to multiple devices, with stability, at an affordable price". 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 RabbitMQ, whereas PubSub+ Event Broker is most compared with IBM MQ, VMware RabbitMQ, ActiveMQ, 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.