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

Apache Flink vs Confluent 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
5th
Average Rating
7.6
Reviews Sentiment
6.9
Number of Reviews
16
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
3rd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
22
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Streaming Analytics category, the mindshare of Apache Flink is 12.4%, up from 10.5% compared to the previous year. The mindshare of Confluent is 8.8%, down from 11.9% 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.
Yantao Zhao - PeerSpot reviewer
Great tool for sharing knowledge, internal communication and allows for real-time collaboration on pages
Confluence is easy to use and modify. However, sometimes there are too many pages. We have to reorganize the folder or parent account. Since everyone can create a page, the same knowledge might be created in multiple places by different people. This leads to redundancy and makes it difficult to find information. It's not centralized. So it could be more user-friendly and centralized. A way to reduce redundancy would be helpful. It's very easy to use, so everyone can create knowledge. But it would be good to synchronize and organize that information a bit better. Another improvement would be in Confluence search. You can search for keywords, but it's not like AI, not even ChatGPT or OpenAI. It would be nice to get more relevant or organized answers. If you're outside the company, you just get some titles containing the keyword you input. But if Confluence were like a database, you could input something and get a well-organized search offering from multiple pages.

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 provides us the flexibility to deploy it on any cluster without being constrained by cloud-based limitations."
"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."
"Easy to deploy and manage."
"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."
"The setup was not too difficult."
"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."
"The design of the product is extremely well built and it is highly configurable."
"The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"The benefit is escaping email communication. Sometimes people ignore emails or put them into spam, but with Confluence, everyone sees the same text at the same time."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
"I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and tools."
"I would rate the scalability of the solution at eight out of ten. We have 20 people who use Confluent in our organization now, and we hope to increase usage in the future."
"The monitoring module is impressive."
 

Cons

"PyFlink is not as fully featured as Python itself, so there are some limitations to what you can do with it."
"There is a learning curve. It takes time to learn."
"In a future release, they could improve on making the error descriptions more clear."
"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."
"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 should improve its data capability and data migration."
"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."
"Currently, in the early stages, I see a gap on the security side. If you are using the SaaS version, we would like to get a fuller, more secure solution that can be adopted right out of the box. Confluence could do a better job sharing best practices or a reusable pattern that others have used, especially for companies that can not afford to hire professional services from Confluent."
"The Schema Registry service could be improved. I would like a bigger knowledge base of other use cases and more technical forums. It would be good to have more flexible monitoring features added to the next release as well."
"In Confluent, there could be a few more VPN options."
"It would help if the knowledge based documents in the support portal could be available for public use as well."
"It could have more integration with different platforms."
"It requires some application specific connectors which are lacking. This needs to be added."
"Confluent's price needs improvement."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
 

Pricing and Cost Advice

"The solution is open-source, which is free."
"It's an open-source solution."
"It's an open source."
"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."
"The solution is cheaper than other products."
"It comes with a high cost."
"Confluent is highly priced."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"Confluence's pricing is quite reasonable, with a cost of around $10 per user that decreases as the number of users increases. Additionally, it's worth noting that for teams of up to 10 users, the solution is completely free."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"The pricing model of Confluent could improve because if you have a classic use case where you're going to use all the features there is no plan to reduce the features. You should be able to pick and choose basic services at a reduced price. The pricing was high for our needs. We should not have to pay for features we do not use."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
831,158 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
17%
Manufacturing Company
6%
Healthcare Company
5%
Financial Services Firm
19%
Computer Software Company
17%
Manufacturing Company
8%
Insurance Company
5%
 

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 Confluent?
I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and to...
What is your experience regarding pricing and costs for Confluent?
Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenanc...
What needs improvement with Confluent?
One area we've identified that could be improved is the governance and access control to the Kafka topics. We've found some limitations, like a threshold of 10,000 rules per cluster, that make it c...
 

Comparisons

 

Also Known As

Flink
No data available
 

Learn More

 

Overview

 

Sample Customers

LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Apache Flink vs. Confluent and other solutions. Updated: January 2025.
831,158 professionals have used our research since 2012.