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

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
6th
Average Rating
7.6
Reviews Sentiment
6.9
Number of Reviews
16
Ranking in other categories
No ranking in other categories
PubSub+ Platform
Ranking in Streaming Analytics
11th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
16
Ranking in other categories
Message Queue (MQ) Software (6th), Message Oriented Middleware (MOM) (2nd), Event Monitoring (10th)
 

Mindshare comparison

As of April 2025, in the Streaming Analytics category, the mindshare of Apache Flink is 13.2%, up from 9.5% compared to the previous year. The mindshare of PubSub+ Platform is 2.8%, down from 3.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics
 

Featured Reviews

Ilya Afanasyev - PeerSpot reviewer
A great solution with an intricate system and allows for batch data processing
We value this solution's intricate system because it comes with a state inside the mechanism and product. The system allows us to process batch data, stream to real-time and build pipelines. Additionally, we do not need to process data from the beginning when we pause, and we can continue from the same point where we stopped. It helps us save time as 95% of our pipelines will now be on Amazon, and we'll save money by saving time.
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.

Quotes from Members

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

Pros

"Apache Flink is meant for low latency applications. You take one event opposite if you want to maintain a certain state. When another event comes and you want to associate those events together, in-memory state management was a key feature for us."
"It is user-friendly and the reporting is good."
"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."
"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."
"Another feature is how Flink handles its radiuses. It has something called the checkpointing concept. You're dealing with billions and billions of requests, so your system is going to fail in large storage systems. Flink handles this by using the concept of checkpointing and savepointing, where they write the aggregated state into some separate storage. So in case of failure, you can basically recall from that state and come back."
"With Flink, it provides out-of-the-box checkpointing and state management. It helps us in that way. When Storm used to restart, sometimes we would lose messages. With Flink, it provides guaranteed message processing, which helped us. It also helped us with maintenance or restarts."
"Allows us to process batch data, stream to real-time and build pipelines."
"It provides us the flexibility to deploy it on any cluster without being constrained by cloud-based limitations."
"The way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
"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 valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"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."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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 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

"There is room for improvement in the initial setup process."
"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."
"The state maintains checkpoints and they use RocksDB or S3. They are good but sometimes the performance is affected when you use RocksDB for checkpointing."
"Apache Flink's documentation should be available in more languages."
"The solution could be more user-friendly."
"The machine learning library is not very flexible."
"Amazon's CloudFormation templates don't allow for direct deployment in the private subnet."
"There are more libraries that are missing and also maybe more capabilities for machine learning."
"The deployment process is complex."
"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."
"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."
"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."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"If you create one event in the past, you cannot resend it."
"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."
"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."
 

Pricing and Cost Advice

"This is an open-source platform that can be used free of charge."
"It's an open-source solution."
"Apache Flink is open source so we pay no licensing for the use of the software."
"It's an open source."
"The solution is open-source, which is free."
"It could be cheaper. Its licensing is on a yearly basis."
"I would rate the product's pricing a ten out of ten."
"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."
"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 the solution 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."
"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."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
846,549 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Computer Software Company
16%
Manufacturing Company
7%
Retailer
4%
Financial Services Firm
36%
Computer Software Company
12%
Retailer
8%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Apache Flink?
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. ...
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?
There are more libraries that are missing and also maybe more capabilities for machine learning. It could have a friendly user interface for pipeline configuration, deployment, and monitoring.
What do you like most about PubSub+ Event Broker?
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.
What needs improvement with PubSub+ Event Broker?
The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively. Additionally, providing a comprehensive dashboard t...
 

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: March 2025.
846,549 professionals have used our research since 2012.