No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Flink vs PubSub+ Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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

Apache Flink
Ranking in Streaming Analytics
4th
Average Rating
7.8
Reviews Sentiment
6.7
Number of Reviews
19
Ranking in other categories
No ranking in other categories
PubSub+ Platform
Ranking in Streaming Analytics
15th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
19
Ranking in other categories
Message Queue (MQ) Software (9th), Message Oriented Middleware (MOM) (2nd), Event Monitoring (11th)
 

Mindshare comparison

As of June 2026, in the Streaming Analytics category, the mindshare of Apache Flink is 8.2%, down from 13.7% compared to the previous year. The mindshare of PubSub+ Platform is 3.7%, up from 2.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Flink8.2%
PubSub+ Platform3.7%
Other88.1%
Streaming Analytics
 

Featured Reviews

Sanjay Srivastava - PeerSpot reviewer
Software Architect at IBM
Streaming workflows have improved data integration and support real-time pipelines across platforms
We are not using Apache Flink in its advanced window capabilities. We are using the Apache Flink job in Apache SeaTunnel, meaning we can write the code inside Apache SeaTunnel. Currently, we are moving; both solutions are there. We are doing it on-premises with the help of Kubernetes and OpenShift. The main reason why Apache Flink is better is that it has more functions, and being open source with easy code in Apache SeaTunnel helps us achieve that. Cost is a major issue. I would rate the stability of the product as an eight. For Apache Flink, the final point can be rated an eight. I can recommend Apache Flink to other users for streaming support, and I am recommending it. I would rate this review an eight overall.
Deepankar Bbhowmick - PeerSpot reviewer
Integration Architect at a tech services company with 11-50 employees
Messaging design has become visual and reliable and now supports fast microservice communication
The unique functions I appreciate about PubSub+ Platform are that it allows me to design my solution in a graphical manner, which is not available in many other products, and the design can also be pushed to the actual infrastructure layer, making it quite advantageous. Mesh technology is useful in scenarios where different geographies have to be connected, although such situations are not commonly found. It is beneficial but not a super-used feature of PubSub+ Platform. The event replay function is quite mature in PubSub+ Platform, allowing me to replay messages that are days in the past, which is a good feature. The main benefits PubSub+ Platform provides for the end-user include building a robust and scalable system with very low network latency, which improves the customer experience, whether using mobile phones or applications. This type of messaging framework is extremely important, and Solace is a very good product in that space. Nowadays, most applications are built using microservices technology, with small microservices interchanging messages via PubSub+ Platform. Without it, realizing a scalable system would not be possible; for example, one cannot have Netflix or similar services that require quick data transit and a good user experience, ensuring that data cannot be lost in transit. The analytics part of PubSub+ Platform is quite useful as it can connect with many analytical software tools, mainly for analysis of system logs, such as Splunk, DataDog, or Prometheus. It has the flexibility to connect with any of these and supports OpenTelemetry, which is not available in many other products, making traceability very easy. I can see how a message travels from a source system to the target system, end-to-end, along with what happens to that message along the path, making the analytics quite good.

Quotes from Members

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

Pros

"Apache Flink's best feature is its data streaming tool."
"The product helps us to create both simple and complex data processing tasks. Over time, it has facilitated integration and navigation across multiple data sources tailored to each client's needs. We use Apache Flink to control our clients' installations."
"We are very happy with the product, and we have been able to achieve all of the use cases that we are expected to deliver for our customers."
"It is user-friendly and the reporting is good."
"Flink moved on to becoming a standard technology for location platform."
"Apache Flink provides faster and low-cost investment for me; I find it to have low hardware requirements, and it's faster with low code, meaning it's easy to understand for moving the streaming data."
"Apache Flink allows you to reduce latency and process data in real-time, making it ideal for such scenarios."
"What I appreciate best about Apache Flink is that it's open source and geared towards a distributed stream processing framework."
"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."
"I rate the PubSub+ Platform a 9 out of 10."
"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."
"With all these new features in place it increases our productivity by something like 50 percent."
"Because we use it as a message broker, it makes information flow very seamless."
"We have seen at least a 50 percent increase in productivity (compared to using Kafka) when using Solace for sharing changes in real-time, onboarding new subscribers, and modifying data sets."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"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."
 

Cons

"One way to improve Flink would be to enhance integration between different ecosystems. For example, there could be more integration with other big data vendors and platforms similar in scope to how Apache Flink works with Cloudera. Apache Flink is a part of the same ecosystem as Cloudera, and for batch processing it's actually very useful but for real-time processing there could be more development with regards to the big data capabilities amongst the various ecosystems out there."
"Failure is another area where it is a bit rigid or not that flexible."
"The solution could be more user-friendly."
"The technical support from Apache is not good; support needs to be improved. I would rate them from one to ten as not good."
"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."
"Amazon's CloudFormation templates don't allow for direct deployment in the private subnet."
"There is room for improvement in the initial setup process."
"In a future release, they could improve on making the error descriptions more clear."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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 product should allow third-party agents to be installed. Currently, it is quite proprietary."
"The integrations could improve in PubSub+ Event Broker."
"We have requested to be able to get into the payload to do dynamic topic hierarchy building."
"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."
"The deployment process is complex."
"Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better."
 

Pricing and Cost Advice

"It's an open source."
"This is an open-source platform that can be used free of charge."
"Apache Flink is open source so we pay no licensing for the use of the software."
"It's an open-source solution."
"The solution is open-source, which is free."
"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."
"The price of the solution is expensive."
"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."
"I would rate the product's pricing a ten out of ten."
"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."
"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."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"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."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Retailer
13%
Computer Software Company
9%
Manufacturing Company
5%
Financial Services Firm
19%
Manufacturing Company
12%
Construction Company
7%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise12
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise15
 

Questions from the Community

What is your experience regarding pricing and costs for Apache Flink?
The solution is expensive. I rate the product’s pricing a nine out of ten, where one is cheap and ten is expensive.
What needs improvement with Apache Flink?
Apache could improve Apache Flink by providing more functionality, as they need to fully support data integration. The connectors are still very few for Apache Flink. There is a lack of functionali...
What is your primary use case for Apache Flink?
I am working with Apache Flink, which is the tool we use for data integration. Apache Flink is for data, and we are working on the data integration project, not big data, using Apache Flink and Apa...
What is your experience regarding pricing and costs for PubSub+ Event Broker?
Pricing-wise for PubSub+ Platform, I find it a little expensive, so I would rate it at six.
What needs improvement with PubSub+ Event Broker?
Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better. While simple authentication using basic methods is easy, moving to more robust...
What is your primary use case for PubSub+ Event Broker?
PubSub+ Platform is primarily used for guaranteed delivery of messages from across systems, for microservice-based development, and for high-speed data consumption purposes. Guaranteed transmission...
 

Also Known As

Flink
PubSub+ Event Broker, PubSub+ Event Portal
 

Overview

 

Sample Customers

LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
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 
Find out what your peers are saying about Apache Flink vs. PubSub+ Platform and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.