Apache Flink vs PubSub+ Platform comparison

Apache and Solace are both solutions in the Streaming Analytics category. Apache is ranked #5 with an average rating of 7.6, while Solace is ranked #11 with an average rating of 8.3. Additionally, 94% of Apache users are willing to recommend the solution, compared to 100% of Solace users who would recommend it.

Apache Flink

Read 16 Apache Flink reviews

7,904 Views
5,490 Comparison Views

94% willing to recommend

PubSub+ Platform

Read 16 PubSub+ Platform reviews

2,039 Views
1,605 Comparison Views

100% willing to recommend

Apache Flink

PubSub+ Platform

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Apache Flink and PubSub+ Platform based on real PeerSpot user reviews.

Find out in this report how the two Streaming Analytics solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.

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

Buyer's Guide

Apache Flink vs. PubSub+ Platform

October 2024

Download the complete report

Helped 813,418 peers since 2012

Categories and Ranking

Apache Flink

Ranking in Streaming Analytics

5th

Average Rating

7.6

Number of Reviews

Ranking in other categories

No ranking in other categories

PubSub+ Platform

Ranking in Streaming Analytics

11th

Average Rating

8.6

Number of Reviews

Ranking in other categories

Message Queue (MQ) Software (7th), Message Oriented Middleware (MOM) (2nd), Event Monitoring (10th)

Featured Reviews

Sunil Morya

Consultant at Tata Consultancy

Nov 18, 2022

Easy to deploy and manage; lacking simple integration with Amazon products

The issue we had with Flink was that when you had to refer the schema into the input data stream, it had to be done directly into code. The XLS format where the schema is stored, had to be stored in Python. If the schema changes, you have to redeploy Flink because the basic tasks and jobs are already running. That's one disadvantage. Another was a restriction with Amazon's CloudFormation templates which don't allow for direct deployment in the private subnet. You have to deploy into the public subnet and then from the Amazon console, specify a different private subnet that requires a lot of settings. In general, the integration with Amazon products was not good and was very time-consuming. I'd like to think that has changed.

Read full review

BhanuChidigam

Sofware Engineering Manager at Wells Fargo

Apr 20, 2023

Performs well, high availability, and helpful support

We are using PubSub+ Event Broker for specific application processing. We have used the solution In banking systems The speed of the throughout has been helpful for our organization. The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption. The…

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

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

"Easy to deploy and manage."

"This is truly a real-time solution."

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

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

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

"Apache Flink offers a range of powerful configurations and experiences for development teams. Its strength lies in its development experience and capabilities."

More Apache Flink pros

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

"In my assessment of Solace against other products — as I was responsible for evaluating various products and bringing the right tool into companies in the past — I worked with multiple platforms like RabbitMQ, Confluent, Kafka, and various other tools in the market. But I found the event mesh capability to be a very interesting as well as fulfilling capability, towards what we want to achieve from a digital-integration-strategy point of view... It's distributed, yet it is intelligently connected. It can also span and I can plug and play any number of brokers into the event mesh, so it's a great deal. That's a differentiator."

"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."

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

"We like the seamless flexibility in protocol exchange offering without writing a code."

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

"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."

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

More PubSub+ Platform pros

Cons

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

"The machine learning library is not very flexible."

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

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

"The solution could be more user-friendly."

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

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

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

More Apache Flink cons

"The product should allow third-party agents to be installed. Currently, it is quite proprietary."

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

"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 integrations could improve in PubSub+ Event Broker."

"The deployment process is complex."

"The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."

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

"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."

More PubSub+ Platform cons

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

"It's an open source."

"It's an open-source solution."

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

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

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

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

"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 the solution is expensive."

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

813,418 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

23%

Computer Software Company

17%

Manufacturing Company

Retailer

Financial Services Firm

36%

Computer Software Company

12%

Manufacturing Company

Retailer

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

See all answers

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?

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.

See all answers

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.

See all answers

What is your experience regarding pricing and costs for PubSub+ Event Broker?

The price of the solution is expensive.

See all answers

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

See all answers

Comparisons

Spring Cloud Data Flow vs Apache Flink

Compared 23% of the time

Databricks vs Apache Flink

Compared 22% of the time

Azure Stream Analytics vs Apache Flink

Compared 14% of the time

Amazon Kinesis vs Apache Flink

Compared 11% of the time

Google Cloud Dataflow vs Apache Flink

Compared 7% of the time

More Apache Flink Competitors

Apache Kafka vs PubSub+ Platform

Compared 28% of the time

IBM MQ vs PubSub+ Platform

Compared 21% of the time

ActiveMQ vs PubSub+ Platform

Compared 12% of the time

Confluent vs PubSub+ Platform

Compared 7% of the time

More PubSub+ Platform Competitors

Product Reports

Buyer's Guide

Apache Flink

October 2024

Download Apache Flink product report

Buyer's Guide

PubSub+ Platform

October 2024

Download PubSub+ Platform product report

Also Known As

Flink

PubSub+ Event Broker, PubSub+ Event Portal

Learn More

Apache

Solace

Overview

Apache Flink is an open-source batch and stream data processing engine. It can be used for batch, micro-batch, and real-time processing. Flink is a programming model that combines the benefits of batch processing and streaming analytics by providing a unified programming interface for both data sources, allowing users to write programs that seamlessly switch between the two modes. It can also be used for interactive queries.

Flink can be used as an alternative to MapReduce for executing iterative algorithms on large datasets in parallel. It was developed specifically for large to extremely large data sets that require complex iterative algorithms.

Flink is a fast and reliable framework developed in Java, Scala, and Python. It runs on the cluster that consists of data nodes and managers. It has a rich set of features that can be used out of the box in order to build sophisticated applications.

Flink has a robust API and is ready to be used with Hadoop, Cassandra, Hive, Impala, Kafka, MySQL/MariaDB, Neo4j, as well as any other NoSQL database.

Apache Flink Features

Distributed execution of streaming programs on clusters of computers
Support for multiple data sources and sinks: this includes Hadoop file systems, databases, and other data sources
Streaming SQL query engine with support for windowing functions
Low latency query execution in milliseconds
Runs in a distributed fashion: it can be deployed on multiple machines or nodes to increase performance and reliability of data processing pipelines.
Powerful API that supports both batch and streaming applications
Runs on clusters of commodity hardware with minimal configuration
Can be integrated with other technologies, such as Apache Spark for complex data mining

Apache Flink Benefits

Ease of use: Flink has an intuitive API and provides high-level abstractions for handling data streams. Even beginners in the field can work with the platform with ease.

Fault tolerance: Flink can automatically detect and recover from failures in the system.

Scalability: Flink scales to thousands of nodes. It can run on clusters of any size and the user does not have to worry about managing the cluster.

Reviews from Real Users

Apache Flink stands out among its competitors for a number of reasons. Two major ones are its low latency and its user-friendly interface. PeerSpot users take note of the advantages of these features in their reviews:

The head of data and analytics at a computer software company notes, “The top feature of Apache Flink is its low latency for fast, real-time data. Another great feature is the real-time indicators and alerts which make a big difference when it comes to data processing and analysis.”

Ertugrul A., manager at a computer software company, writes, “It's usable and affordable. It is user-friendly and the reporting is good.”

PubSub+ Platform supports real-time shipment tracking, IT event management in multiclouds, and connects legacy and cloud-native systems for application modernization. It's utilized for trading, streaming market data, and app-to-app messaging, enhancing event-driven architectures with reliable message queuing.

Organizations adopt PubSub+ to efficiently transport events across hybrid and cloud environments, managing audit trails and long processing tasks. The platform aids integration through dynamic data publication, event mesh capabilities, and WAN optimization. Features like seamless integration, protocol agnosticism, and flexible topic hierarchy enhance versatility. Solace Admin Utility simplifies configuration and management, while the event portal allows hybrid deployment.

What are the key features of PubSub+ Platform?

Dynamic Data Publication: Enables flexible and responsive data handling.
Event Mesh Capabilities: Facilitates efficient event transportation.
WAN Optimization: Enhances data transfer across networks.
Protocol Agnosticism: Supports a wide range of protocols for integration.
Flexible Topic Hierarchy: Allows detailed and organized data exchange.
Solace Admin Utility: Provides intuitive configuration and management.
Granular Topic Filtering: Offers precise data filtering options.
Guaranteed Messaging: Ensures reliable message delivery.

What benefits or ROI should users consider?

Seamless Integration: Reduces complexity in connecting systems.
Performance and Scaling: Supports high-load environments efficiently.
Asynchronous Messaging: Improves application performance.
Robust Support System: Provides guidance and problem resolution.

PubSub+ is implemented in industries requiring real-time data handling and integration between disparate systems. Financial institutions use it for trading and streaming market data, while logistics companies benefit from real-time shipment tracking. Enterprises apply it to modernize operations by connecting legacy systems with cloud-native applications, enhancing their architecture and ensuring data reliability across environments.

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

October 2024

Free Report: Apache Flink vs. PubSub+ Platform

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

DOWNLOAD NOW

813,418 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.