We performed a comparison between Apache Spark Streaming and PubSub+ Event Broker based on real PeerSpot user reviews.
Find out in this report how the two Streaming Analytics solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Apache Spark Streaming's most valuable feature is near real-time analytics. The developers can build APIs easily for a code-steaming pipeline. The solutions have an ecosystem of integration with other stock services."
"The solution is very stable and reliable."
"As an open-source solution, using it is basically free."
"It's the fastest solution on the market with low latency data on data transformations."
"The solution is better than average and some of the valuable features include efficiency and stability."
"Apache Spark Streaming was straightforward in terms of maintenance. It was actively developed, and migrating from an older to a newer version was quite simple."
"Apache Spark Streaming is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows."
"Apache Spark Streaming has features like checkpointing and Streaming API that are useful."
"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."
"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."
"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."
"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."
"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 initial setup is quite complex."
"The cost and load-related optimizations are areas where the tool lacks and needs improvement."
"The solution itself could be easier to use."
"We would like to have the ability to do arbitrary stateful functions in Python."
"In terms of improvement, the UI could be better."
"There could be an improvement in the area of the user configuration section, it should be less developer-focused and more business user-focused."
"The service structure of Apache Spark Streaming can improve. There are a lot of issues with memory management and latency. There is no real-time analytics. We recommend it for the use cases where there is a five-second latency, but not for a millisecond, an IOT-based, or the detection anomaly-based. Flink as a service is much better."
"It was resource-intensive, even for small-scale applications."
"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 product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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?"
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"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 licensing and the cost are the major pitfalls."
Apache Spark Streaming is ranked 8th in Streaming Analytics with 8 reviews while PubSub+ Event Broker is ranked 10th in Streaming Analytics with 15 reviews. Apache Spark Streaming is rated 8.0, while PubSub+ Event Broker is rated 8.6. The top reviewer of Apache Spark Streaming writes "Easy integration, beneficial auto-scaling, and good open-sourced support community". 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 Spark Streaming is most compared with Amazon Kinesis, Azure Stream Analytics, Spring Cloud Data Flow, Confluent and Apache Pulsar, whereas PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, VMware RabbitMQ, ActiveMQ and Confluent. See our Apache Spark Streaming vs. PubSub+ Event Broker report.
See our list of best Streaming Analytics vendors.
We monitor all Streaming Analytics 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.
