No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Spark Streaming vs Confluent comparison

Why PeerSpot?
 

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 Spark Streaming
Ranking in Streaming Analytics
8th
Average Rating
7.8
Reviews Sentiment
6.4
Number of Reviews
17
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
7th
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2026, in the Streaming Analytics category, the mindshare of Apache Spark Streaming is 4.6%, up from 3.6% compared to the previous year. The mindshare of Confluent is 6.3%, down from 8.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.3%
Apache Spark Streaming4.6%
Other89.1%
Streaming Analytics
 

Featured Reviews

Khoa Dang Le - PeerSpot reviewer
Principal AI Engineer at IMT Solutions
Have faced challenges with complex data handling and seek smoother integration for machine learning workflows
I find the fault tolerance feature beneficial because I use it for serving data from a landing area. I understand all of the structures we have for Spark SQL, Spark Streaming, and MLlib. The ability of Apache Spark Streaming to handle out-of-order data using watermarking and windowing is something we use in our pipeline. Nearly 50% of our usage is based on that because we use it for landing data, and we appreciate that we can work with it. The main benefits of Apache Spark Streaming include cost savings, time savings, and efficiency improvements about data storage. The fast storage capability is crucial because Apache Spark replaces Hadoop's MapReduce, allowing us to manage our data more efficiently.
PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.

Quotes from Members

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

Pros

"The main benefits of Apache Spark Streaming include cost savings, time savings, and efficiency improvements about data storage."
"By integrating Apache Spark Streaming, the data freshness rate, and latency have significantly improved from 24-hour batch processing to less than one minute, facilitating faster communication to downstream systems, aiding marketing campaigns."
"Apache Spark Streaming's most valuable feature is near real-time analytics. The developers can build APIs easily for a code-steaming pipeline. The solutions have an ecosystem of integration with other stock services."
"With Apache Spark Streaming, you can have multiple kinds of windows; depending on your use case, you can select either a tumbling window, a sliding window, or a static window to determine how much data you want to process at a single point of time."
"Apache Spark Streaming is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows."
"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."
"Apache Spark's capabilities for machine learning are quite extensive and can be used in a low-code way."
"As an open-source solution, using it is basically free."
"As an enterprise organization, data availability is critical and Confluent provides that SLA support."
"The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"Some of the best features are that it's very quick to set up, very easy to have a centralized area that gives us a history of changes, and the ability to give feedback on any information placed onto the pages."
"The documentation process is fast with the tool."
"Having used SharePoint in the past, when I compare with traditional, old document repositories, like SharePoint, I would definitely recommend Confluent."
 

Cons

"One improvement I would expect is real-time processing instead of micro-batch or near real-time."
"We would like to have the ability to do arbitrary stateful functions in Python."
"Monitoring is an area where they could definitely improve Apache Spark Streaming. When you have a streaming application, it generates numerous logs. After some time, the logs become meaningless because they're quite large and impossible to open."
"The problem is we need to use it in a certain manner. After that, we need to apply another pipeline for the machine learning processes, and that's what we work on."
"When dealing with various data types including COBOL, Excel, JSON, video, audio, and MPG files, challenges can arise with incomplete or missing values."
"Integrating event-level streaming capabilities could be beneficial."
"The cost and load-related optimizations are areas where the tool lacks and needs improvement."
"The solution itself could be easier to use."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"It could have more themes. They should also have more reporting-oriented plugins as well. It would be great to have free custom reports that can be dispatched directly from Jira."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"The formatting aspect within the page can be improved and more powerful."
"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 challenging to manage access at scale if we have many different data sources."
"The pricing was high for our needs. We should not have to pay for features we do not use."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"The solution could have an extra plugin or upgrading feature. In addition, it could have more integration with different platforms and be more compatible."
 

Pricing and Cost Advice

"I was using the open-source community version, which was self-hosted."
"On a scale from one to ten, where one is expensive, or not cost-effective, and ten is cheap, I rate the price a seven."
"Spark is an affordable solution, especially considering its open-source nature."
"People pay for Apache Spark Streaming as a service."
"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 is an expensive solution."
"You have to pay additional for one or two features."
"Confluent is highly priced."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"On a scale from one to ten, where one is low pricing and ten is high pricing, I would rate Confluent's pricing at five. I have not encountered any additional costs."
"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."
"It comes with a high cost."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Outsourcing Company
13%
Comms Service Provider
9%
Healthcare Company
6%
Financial Services Firm
14%
Retailer
12%
Manufacturing Company
7%
Computer Software Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise7
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
 

Questions from the Community

What needs improvement with Apache Spark Streaming?
One of the improvements we need is in Spark SQL and the machine learning library. I don't think there is too much to work on, but the issue is when we want to use machine learning, we always need t...
What is your primary use case for Apache Spark Streaming?
We work with Apache Spark Streaming for our project because we use that as one of the landing data sources, and we work with it to ensure we can get all of the data before it goes through our data ...
What advice do you have for others considering Apache Spark Streaming?
One thing I would share with other organizations considering Apache Spark Streaming is the necessity of having effective data storage. We want to ensure we acquire and manage our data storage effec...
What is your experience regarding pricing and costs for Confluent?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
What is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
 

Also Known As

Spark Streaming
No data available
 

Overview

 

Sample Customers

UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, eBay Inc.
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Apache Spark Streaming vs. Confluent and other solutions. Updated: September 2026.
913,806 professionals have used our research since 2012.