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.9
Number of Reviews
18
Ranking in other categories
No ranking in other categories
Apache Pulsar
Ranking in Streaming Analytics
21st
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 September 2025, in the Streaming Analytics category, the mindshare of Apache Flink is 14.6%, up from 10.1% compared to the previous year. The mindshare of Apache Pulsar is 2.3%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Apache Flink14.6%
Apache Pulsar2.3%
Other83.1%
Streaming Analytics
 

Featured Reviews

Aswini Atibudhi - PeerSpot reviewer
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
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

"This is truly a real-time solution."
"It is user-friendly and the reporting is good."
"Easy to deploy and manage."
"The setup was not too difficult."
"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."
"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."
"Allows us to process batch data, stream to real-time and build pipelines."
"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."
"The solution operates as a classic message broker but also as a streaming platform."
 

Cons

"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."
"There are more libraries that are missing and also maybe more capabilities for machine learning."
"In a future release, they could improve on making the error descriptions more clear."
"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."
"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."
"There is a learning curve. It takes time to learn."
"The solution could be more user-friendly."
"There is room for improvement in the initial setup process."
"Documentation is poor because much of it is in Chinese with no English translation."
 

Pricing and Cost Advice

"This is an open-source platform that can be used free of charge."
"It's an open source."
"It's an open-source solution."
"The solution is open-source, which is free."
"Apache Flink is open source so we pay no licensing for the use of the software."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
867,349 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
11%
Retailer
11%
Manufacturing Company
7%
Computer Software Company
20%
Financial Services Firm
12%
Comms Service Provider
8%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise11
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 should provide more examples and sample code related to streaming to help me better adapt and utilize the tool. There is a need for increased awareness and education, especially around best ...
Ask a question
Earn 20 points
 

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), Confluent and others in Streaming Analytics. Updated: August 2025.
867,349 professionals have used our research since 2012.