Try our new research platform with insights from 80,000+ expert users

PubSub+ Platform vs SAS Event Stream Processing comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

PubSub+ Platform
Ranking in Streaming Analytics
11th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
17
Ranking in other categories
Message Queue (MQ) Software (8th), Message Oriented Middleware (MOM) (2nd), Event Monitoring (12th)
SAS Event Stream Processing
Ranking in Streaming Analytics
27th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the Streaming Analytics category, the mindshare of PubSub+ Platform is 2.9%, up from 2.9% compared to the previous year. The mindshare of SAS Event Stream Processing is 0.5%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics
 

Featured Reviews

BhanuChidigam - PeerSpot reviewer
Performs well, high availability, and helpful support
We use approximately four people for the maintenance of the solution. My advice to others is this solution has high throughput and is used for many stock exchanges. For business critical use cases, such as processing financial transactions at a quick speed, I would recommend this solution. I rate PubSub+ Event Broker an eight out of ten.
Roi Jason Buela - PeerSpot reviewer
A solution with useful windowing features and great for operations and marketing
The persistence could be better. Although ESP is designed for in-memory processing, it would be better if the solution is enhanced or improved on the persistence of the data that is kept in the memory. For example, if one server goes down and the information is stored in the memory, it is lost. Therefore, the persistence needs to be improved so that if there are more cases where the server is down, the information and data can still be intact.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"Some valuable features include reconnecting topics, placing queues, and direct connections to MongoDB. The platform provides a dashboard to monitor the status of messages, such as how many have been processed or delivered, which is helpful for tracking performance."
"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."
"The solution is beneficial on an enterprise level."
 

Cons

"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."
"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."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"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 heard that it is quite expensive compared to Kafka."
"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."
"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?"
"The persistence could be better."
 

Pricing and Cost Advice

"There are different tiers where you can choose what would work for you. As a customer, you need to know roughly how many messages a month you will use."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"The price of the solution is expensive."
"Having a free version of the solution was a big, important part of our decision to go with it. This was the big driver for us to evaluate Solace. We started using it as the free version. When we felt comfortable with the free version, that is when we bought the enterprise version."
"We have been really happy with the product licensing rates. It has been free for us, up to a 100,000 transactions per second, and all we have to do is pay for support. Making their product available and accessible to us has not been a problem at all."
"We are looking for something that will add value and fit for purpose. Freeware is good if you want to try something quickly without putting in much money. However, as far as our decision is concerned, I don't think it helps. At the end of the day, if we are convinced that a capability is required, we will ask for the funding. Then, when the funding is available, we will go for an enterprise solution only."
"The price of PubSub+ Event Broker is reasonable for the capability it offers. However, when compared to others solutions on the market it is expensive."
"Having a free version is critical for our technology operations use case. This is primarily because our technology operations team is a cost center in our company. They are not profit drivers and having a free version for installation will probably meet our needs. Even for production, it'll support up to a 100,000 messages per second. I don't think in technology operations that we have that many events and alerts from our detection tools. Even if I have 20 or 30 event detection products out there, they're only going to publish the things which are critical or warnings. I don't think we'll ever reach a 100,000 messages per second."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
861,481 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
33%
Computer Software Company
11%
Manufacturing Company
8%
Retailer
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with PubSub+ Event Broker?
Regarding improving the PubSub+ Platform, I'm not sure about the pricing aspect, but I heard that it is quite expensive compared to Kafka. That's the only concern I can mention; otherwise, it was a...
What is your primary use case for PubSub+ Event Broker?
My typical use case for the PubSub+ Platform is as an event-driven solution for communication between two components.
What advice do you have for others considering PubSub+ Event Broker?
I have experience working with Kafka, PubSub+ Platform, and IBM MQ, all three of them. We are customers, meaning my company uses Solace. We use it and customize it based on our needs. Based on my e...
Ask a question
Earn 20 points
 

Also Known As

PubSub+ Event Broker, PubSub+ Event Portal
No data available
 

Overview

 

Sample Customers

FxPro, TP ICAP, Barclays, Airtel, American Express, Cobalt, Legal & General, LSE Group, Akuna Capital, Azure Information Technology, Brand.net, Canadian Securities Exchange, Core Transport Technologies, Crédit Agricole, Fluent Trade Technologies, Harris Corporation, Korea Exchange, Live E!, Mercuria Energy, Myspace, NYSE Technologies, Pico, RBC Capital Markets, Standard Chartered Bank, Unibet 
Honda, HSBC, Lufthansa, Nestle, 89Degrees.
Find out what your peers are saying about Databricks, Amazon Web Services (AWS), Microsoft and others in Streaming Analytics. Updated: July 2025.
861,481 professionals have used our research since 2012.