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

"The ease of usage, even for complex tasks, stands out."
"The documentation is very good."
"The event processing function is the most useful or the most used function. The filter function and the mapping function are also very useful because we have a lot of data to transform. For example, we store a lot of information about a person, and when we want to retrieve this person's details, we need all the details. In the map function, we can actually map all persons based on their age group. That's why the mapping function is very useful. We can really get a lot of events, and then we keep on doing what we need to do."
"What I appreciate best about Apache Flink is that it's open source and geared towards a distributed stream processing framework."
"Allows us to process batch data, stream to real-time and build pipelines."
"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."
"The main advantage is the turnaround time, which has been reduced drastically because of Apache Flink, and now everything is in almost real time with no waiting or lag of data in the application while machine resources are utilized much more efficiently."
"We value this solution's intricate system because it comes with a state inside the mechanism and product, allowing us to process batch data, stream to real-time and build pipelines, and we do not need to process data from the beginning when we pause as we can continue from the same point where we stopped, helping us save time as 95% of our pipelines will now be on Amazon and we'll save money by saving time."
"The best features of PubSub+ Platform include being highly scalable, allowing us to handle billions and billions of events, and configuring and managing PubSub+ Platform is straightforward and simple while being highly reliable."
"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."
"If we talk about Solace, you see the value-add layer; I can say that Solace is a basic Kafka, but on top of that Kafka layer, they have added their own layer that is really good, as this is where it adds value and why we went for it."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"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."
"It is a product that is more like a switch or router, where you install it, then it keeps on working."
"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

"In a future release, they could improve on making the error descriptions more clear."
"Apache Flink's documentation should be available in more languages."
"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."
"The solution could be more user-friendly."
"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."
"In terms of stability with Flink, it is something that you have to deal with every time. Stability is the number one problem that we have seen with Flink, and it really depends on the kind of problem that you're trying to solve."
"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."
"The technical support from Apache is not good; support needs to be improved. I would rate them from one to ten as not good."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"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."
"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 solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"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 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."
"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."
"If you create one event in the past, you cannot resend it."
 

Pricing and Cost Advice

"The solution is open-source, which is free."
"Apache Flink is open source so we pay no licensing for the use of the software."
"This is an open-source platform that can be used free of charge."
"It's an open-source solution."
"It's an open source."
"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."
"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."
"I would rate the product's pricing a ten out of ten."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"The licensing is dependent on the volume that is flowing. If you go for their support services, it will cost some more money, but I think it is worth it, especially if you are just starting your journey."
"It could be cheaper. Its licensing is on a yearly basis."
"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."
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.