Apache Flink vs PubSub+ Platform comparison

Apache and Solace are both solutions in the Streaming Analytics category. Apache is ranked #4 with an average rating of 8.0, while Solace is ranked #15 with an average rating of 8.5. Apache holds a 8.2% mindshare in SA, compared to Solace’s 3.7% mindshare. Additionally, 95% of Apache users are willing to recommend the solution, compared to 100% of Solace users who would recommend it.

Apache Flink

Read 19 Apache Flink reviews

4,639 Views
4,639 Comparison Views

95% willing to recommend

PubSub+ Platform

Read 19 PubSub+ Platform reviews

4,179 Views
1,797 Comparison Views

100% willing to recommend

Apache Flink

PubSub+ Platform

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

Apache Flink and PubSub+ Platform are both key players in the real-time data processing category. Apache Flink appears to have the upper hand in stream processing capabilities, while PubSub+ Platform is preferred for its robust messaging features.

Features:Apache Flink is known for stateful computation, high throughput, and precise low-latency operations, making it ideal for intricate real-time analytics. PubSub+ Platform is notable for its versatile message brokering, support of multiple messaging protocols, and dynamic message routing, which effectively addresses event-driven architecture needs.

Room for Improvement:Apache Flink can benefit from improved ease of use, more intuitive community support, and reduced deployment complexity. PubSub+ Platform could enhance its integration features, broaden its protocol support, and optimize its cost structure for better market competitiveness.

Ease of Deployment and Customer Service:Apache Flink offers deployment on various platforms such as Kubernetes but requires technical expertise, and its community-based support model may deter some users. PubSub+ Platform provides more accessible cloud-native deployment options with strong professional support, favorable for organizations seeking managed solutions.

Pricing and ROI:Apache Flink offers a lower setup cost, attributed to its open-source nature, which is ideal for users focused on cost-effective real-time analytics. PubSub+ Platform, while having potentially higher initial costs, ensures a solid ROI through its comprehensive messaging capabilities and outstanding support, making it a beneficial choice for event-driven applications.

To learn more, read our detailed Apache Flink vs. PubSub+ Platform Report (Updated: June 2026).

Buyer's Guide

Apache Flink vs. PubSub+ Platform

June 2026

Download the complete report

Helped 900,644 peers since 2012

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

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

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
Product	Mindshare (%)
Apache Flink	8.2%
PubSub+ Platform	3.7%
Other	88.1%

Streaming Analytics

Featured Reviews

Sanjay Srivastava

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.

Read full review

Deepankar Bbhowmick

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.

Read full review

Quotes from Members

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

Pros

"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."

"This is truly a real-time solution."

"Apache Flink allows you to reduce latency and process data in real-time, making it ideal for such scenarios."

"The end-to-end latency was drastically reduced, and our capability of handling high throughput has increased by using Flink."

"Apache Flink's best feature is its data streaming tool."

"Allows us to process batch data, stream to real-time and build pipelines."

"Easy to deploy and manage."

"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."

More Apache Flink pros

"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."

"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."

"The way we can replicate information and send it to several subscribers is most valuable."

"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 valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."

"With all these new features in place it increases our productivity by something like 50 percent."

"Capital markets couldn't operate today if Solace were down."

"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."

More PubSub+ Platform pros

Cons

"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."

"There is a learning curve. It takes time to learn."

"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."

"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."

"Flink has become a lot more stable but the machine learning library is still not very flexible."

"The TimeWindow feature is a bit tricky. The timing of the content and the windowing is a bit changed in 1.11. They have introduced watermarks. A watermark is basically associating every data with a timestamp. The timestamp could be anything, and we can provide the timestamp. So, whenever I receive a tweet, I can actually assign a timestamp, like what time did I get that tweet. The watermark helps us to uniquely identify the data. Watermarks are tricky if you use multiple events in the pipeline. For example, you have three resources from different locations, and you want to combine all those inputs and also perform some kind of logic. When you have more than one input screen and you want to collect all the information together, you have to apply TimeWindow all. That means that all the events from the upstream or from the up sources should be in that TimeWindow, and they were coming back. Internally, it is a batch of events that may be getting collected every five minutes or whatever timing is given. Sometimes, the use case for TimeWindow is a bit tricky. It depends on the application as well as on how people have given this TimeWindow. This kind of documentation is not updated. Even the test case documentation is a bit wrong. It doesn't work. Flink has updated the version of Apache Flink, but they have not updated the testing documentation. Therefore, I have to manually understand it. We have also been exploring failure handling. I was looking into changelogs for which they have posted the future plans and what are they going to deliver. We have two concerns regarding this, which have been noted down. I hope in the future that they will provide this functionality. Integration of Apache Flink with other metric services or failure handling data tools needs some kind of update or its in-depth knowledge is required in the documentation. We have a use case where we want to actually analyze or get analytics about how much data we process and how many failures we have. For that, we need to use Tomcat, which is an analytics tool for implementing counters. We can manage reports in the analyzer. This kind of integration is pretty much straightforward. They say that people must be well familiar with all the things before using this type of integration. They have given this complete file, which you can update, but it took some time. There is a learning curve with it, which consumed a lot of time. It is evolving to a newer version, but the documentation is not demonstrating that update. The documentation is not well incorporated. Hopefully, these things will get resolved now that they are implementing it. Failure is another area where it is a bit rigid or not that flexible. We never use this for scaling because complexity is very high in case of a failure. Processing and providing the scaled data back to Apache Flink is a bit challenging. They have this concept of offsetting, which could be simplified."

"Apache Flink's documentation should be available in more languages."

"There is room for improvement in the initial setup process."

More Apache Flink cons

"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?"

"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."

"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 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."

"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."

"Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better."

"I heard that it is quite expensive compared to Kafka."

"If you create one event in the past, you cannot resend it."

More PubSub+ Platform cons

Pricing and Cost Advice

"Apache Flink is open source so we pay no licensing for the use of the software."

"The solution is open-source, which is free."

"It's an open source."

"This is an open-source platform that can be used free of charge."

"It's an open-source solution."

"I would rate the product's pricing a ten out of ten."

"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."

"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."

"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."

"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."

More PubSub+ Platform pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.

See recommendations

900,644 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

19%

Retailer

13%

Computer Software Company

Manufacturing Company

Financial Services Firm

19%

Manufacturing Company

12%

Construction Company

Retailer

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	5
Midsize Enterprise	3
Large Enterprise	12

By reviewers
Company Size	Count
Small Business	5
Midsize Enterprise	1
Large Enterprise	15

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.

See all answers

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...

See all answers

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...

See all answers

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.

See all answers

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...

See all answers

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...

See all answers

Comparisons

Spring Cloud Data Flow vs Apache Flink

Compared 9% of the time

Azure Stream Analytics vs Apache Flink

Compared 9% of the time

Amazon Kinesis vs Apache Flink

Compared 8% of the time

Confluent vs Apache Flink

Compared 7% of the time

Apache Spark Streaming vs Apache Flink

Compared 4% of the time

More Apache Flink Competitors

Apache Kafka vs PubSub+ Platform

Compared 8% of the time

Azure Stream Analytics vs PubSub+ Platform

Compared 6% of the time

IBM MQ vs PubSub+ Platform

Compared 6% of the time

Confluent vs PubSub+ Platform

Compared 6% of the time

Aurea CX Messenger vs PubSub+ Platform

Compared 4% of the time

More PubSub+ Platform Competitors

Product Reports

Buyer's Guide

Apache Flink

June 2026

Download Apache Flink product report

Buyer's Guide

PubSub+ Platform

June 2026

Download PubSub+ Platform product report

Also Known As

Flink

PubSub+ Event Broker, PubSub+ Event Portal

Overview

Apache Flink is a powerful open-source framework for stateful computations over data streams, designed for both real-time and batch processing. It efficiently handles massive volumes of data with low-latency responses, offering versatility for complex event processing scenarios.

Apache Flink excels in processing high-throughput data streams, enabling seamless state management across distributed applications. Users appreciate its robust features like stateful transformations and checkpointing, simplifying deployment in diverse environments. Though powerful, it poses challenges for beginners due to its complexity and limited documentation, requiring some prior experience to master. Its flexible integration with systems like Kafka and support for Kubernetes on AWS makes it suitable for demanding environments where quick, real-time analysis is essential.

What are the key features of Apache Flink?

Stateful Transformations: Allows complex stateful operations on data streams with precise handling.
Low Latency: Ensures real-time data processing with minimal delays.
Checkpointing: Provides efficient and reliable checkpointing for fault tolerance.
Kafka Integration: Easy integration with Kafka for seamless data ingestion and processing.
API Support: Provides robust APIs for diverse data processing needs.
Flexible Deployment: Offers options for deploying on-premise or in cloud environments.

What benefits should users look for?

Versatility: Supports both batch and stream processing in a unified model.
Community Support: Backed by an active community that continuously enhances its features.
Ease of Use: Simplifies the coding process compared to similar frameworks like Apache Storm.
Real-Time Analytics: Facilitates immediate insights and data-driven decision-making.

Organizations leverage Apache Flink primarily for real-time data processing in sectors such as retail, transportation, and telecommunications. By deploying on AWS with Kubernetes, companies can utilize it for data cleaning, generating customer insights, and providing swift real-time updates. It effectively manages millions of events per second, serving use cases like cab aggregations, map-making, and outlier detection in telecom networks, enabling seamless integration of streaming data with existing pipelines.

Apache

PubSub+ Platform is designed for real-time message publishing and outstanding interoperability. With features like intuitive administration and topic filtering, it offers both stability and high performance for scalable deployments across diverse scenarios.

PubSub+ Platform enhances data integration with its event mesh and seamless protocol compatibility, providing a comprehensive solution for organizations tracking shipments, generating reports, and managing transactions. Its granular topic filtering and WAN optimization ensure high utility in event-driven applications and cloud deployments. Users highlight the platform's intuitive administration and ease of management, though some seek improved integration with third-party tools and enhanced observability. Concerns include scalability for large payloads and training resource availability. Despite its interface complexity, PubSub+ remains valuable for trading and market data distribution.

What are the key features of PubSub+ Platform?

Real-time messaging: Facilitates seamless communication across platforms.
Flexible topic hierarchy: Supports dynamic topic taxonomy for efficient data management.
Event mesh: Enhances integration and interoperability with diverse protocols.
Intuitive administration: Simplifies system management and configuration.
WAN optimization: Ensures efficient connectivity for global deployment.

What benefits should users look for in reviews?

Messaging stability: Offers consistent performance in dynamic environments.
Scalability: Provides seamless expansion to accommodate growing data volumes.
Security: Maintains robust protection for sensitive information.
Support and configuration: Accessible, reliable support, and UI-driven setup streamline the management.

PubSub+ Platform is widely implemented for asynchronous messaging in industries like finance for trading and market data, logistics for shipment tracking, and tech operations management. It enables companies to modernize applications while ensuring data accuracy and efficiency across global systems.

Solace

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

Buyer's Guide

Apache Flink vs. PubSub+ Platform

June 2026

Free Report: Apache Flink vs. PubSub+ Platform

Find out what your peers are saying about Apache Flink vs. PubSub+ Platform and other solutions. Updated: June 2026.

DOWNLOAD NOW

900,644 professionals have used our research since 2012.

See our Apache Flink vs. PubSub+ Platform 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.