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

Apache Flink vs Apache Pulsar comparison

 

Comparison Buyer's Guide

Executive Summary

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
Apache Pulsar
Ranking in Streaming Analytics
22nd
Average Rating
8.0
Reviews Sentiment
6.2
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Streaming Analytics category, the mindshare of Apache Flink is 12.3%, up from 11.6% compared to the previous year. The mindshare of Apache Pulsar is 2.6%, up from 2.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Apache Flink12.3%
Apache Pulsar2.6%
Other85.1%
Streaming Analytics
 

Featured Reviews

Aswini Atibudhi - PeerSpot reviewer
Distinguished AI Leader at Walmart Global Tech at Walmart
Enables robust real-time data processing but documentation needs refinement
Apache Flink is very powerful, but it can be challenging for beginners because it requires prior experience with similar tools and technologies, such as Kafka and batch processing. It's essential to have a clear foundation; hence, it can be tough for beginners. However, once they grasp the concepts and have examples or references, it becomes easier. Intermediate users who are integrating with Kafka or other sources may find it smoother. After setting up and understanding the concepts, it becomes quite stable and scalable, allowing for customization of jobs. Every software, including Apache Flink, has room for improvement as it evolves. One key area for enhancement is user-friendliness and the developer experience; improving documentation and API specifications is essential, as they can currently be verbose and complex. Debugging and local testing pose challenges for newcomers, particularly when learning about concepts such as time semantics and state handling. Although the APIs exist, they aren't intuitive enough. We also need to simplify operational procedures, such as developing tools and tuning Flink clusters, as these processes can be quite complex. Additionally, implementing one-click rollback for failures and improving state management during dynamic scaling while retaining the last states is vital, as the current large states pose scaling challenges.
it_user1087029 - PeerSpot reviewer
Solution Architect at Vlaanderen connect.
The solution can mimic other APIs without changing a line of code
The solution operates as a classic message broker but also as a streaming platform. It operates differently than a traditional streaming platform with storage and computing handled separately. It scales easier and better than Kafka which can be stubborn. You can even make it act like Kafka because it understands Kafka APIs. There are even companies that will sell you Kafka but underneath it is Apache Pulsar. The solution is very compatible because it can mimic other APIs without changing a line of code.

Quotes from Members

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

Pros

"Allows us to process batch data, stream to real-time and build pipelines."
"This is truly a real-time solution."
"What I appreciate best about Apache Flink is that it's open source and geared towards a distributed stream processing framework."
"It provides us the flexibility to deploy it on any cluster without being constrained by cloud-based limitations."
"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."
"Apache Flink allows you to reduce latency and process data in real-time, making it ideal for such scenarios."
"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."
"Apache Flink's best feature is its data streaming tool."
"The solution operates as a classic message broker but also as a streaming platform."
 

Cons

"There are more libraries that are missing and also maybe more capabilities for machine learning."
"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."
"The machine learning library is not very flexible."
"Apache Flink is very powerful, but it can be challenging for beginners because it requires prior experience with similar tools and technologies, such as Kafka and batch processing."
"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."
"Apache Flink should improve its data capability and data migration."
"The solution could be more user-friendly."
"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."
"Documentation is poor because much of it is in Chinese with no English translation."
 

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."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Retailer
12%
Computer Software Company
10%
Manufacturing Company
6%
Financial Services Firm
17%
Computer Software Company
12%
Insurance Company
7%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise12
No data available
 

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?
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...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Flink
No data available
 

Overview

 

Sample Customers

LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
Information Not Available
Find out what your peers are saying about Databricks, Amazon Web Services (AWS), Microsoft and others in Streaming Analytics. Updated: January 2026.
881,082 professionals have used our research since 2012.