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

Apache Spark Streaming 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 Spark Streaming
Ranking in Streaming Analytics
10th
Average Rating
8.0
Reviews Sentiment
7.4
Number of Reviews
11
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
4th
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
23
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Streaming Analytics category, the mindshare of Apache Spark Streaming is 2.7%, down from 3.8% compared to the previous year. The mindshare of Confluent is 8.5%, down from 11.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics
 

Featured Reviews

AbhishekGupta - PeerSpot reviewer
Easy integration, beneficial auto-scaling, and good open-sourced support community
The service structure of Apache Spark Streaming can improve. There are a lot of issues with memory management and latency. There is no real-time analytics. We recommend it for the use cases where there is a five-second latency, but not for a millisecond, an IOT-based, or the detection anomaly-based. Flink as a service is much better. Apache Spark Streaming does not have auto-tuning. A customer needs to invest a lot, in terms of management and maintenance.
Gustavo-Barbosa Dos Santos - PeerSpot reviewer
Has good technical support services and a valuable feature for real-time data streaming
Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance. It helps us understand the various requirements of multiple customers and validates the information for different versions. We can automate the tasks using Confluent Kafka. Thus, it guarantees us the data quality and maintains the integrity of message contracts.

Quotes from Members

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

Pros

"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."
"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."
"The solution is very stable and reliable."
"Spark Streaming is critical, quite stable, full-featured, and scalable."
"The solution is better than average and some of the valuable features include efficiency and stability."
"Apache Spark Streaming is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows."
"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."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"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."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
"The most valuable feature that we are using is the data replication between the data centers allowing us to configure a disaster recovery or software. However, is it's not mandatory to use and because most of the features that we use are from Apache Kafka, such as end-to-end encryption. Internally, we can develop our own kind of product or service from Apache Kafka."
"The client APIs are the most valuable feature."
"A person with a good IT background and HTML will not have any trouble with Confluent."
"Their tech support is amazing; they are very good, both on and off-site."
"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."
 

Cons

"The solution itself could be easier to use."
"Integrating event-level streaming capabilities could be beneficial."
"We would like to have the ability to do arbitrary stateful functions in Python."
"The debugging aspect could use some improvement."
"In terms of improvement, the UI could be better."
"It was resource-intensive, even for small-scale applications."
"The cost and load-related optimizations are areas where the tool lacks and needs improvement."
"The service structure of Apache Spark Streaming can improve. There are a lot of issues with memory management and latency. There is no real-time analytics. We recommend it for the use cases where there is a five-second latency, but not for a millisecond, an IOT-based, or the detection anomaly-based. Flink as a service is much better."
"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."
"There is no local support team in Saudi Arabia."
"We continuously face issues, such as Kafka being down and slow responses from the support team."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"It could have more integration with different platforms."
"there is room for improvement in the visualization."
"They should remove Zookeeper because of security issues."
 

Pricing and Cost Advice

"Spark is an affordable solution, especially considering its open-source nature."
"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."
"People pay for Apache Spark Streaming as a service."
"Confluent is highly priced."
"Confluent is an expensive solution."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"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."
"You have to pay additional for one or two features."
"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."
"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."
"The solution is cheaper than other products."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
848,253 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
19%
Manufacturing Company
6%
University
5%
Financial Services Firm
19%
Computer Software Company
16%
Manufacturing Company
7%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Apache Spark Streaming?
Apache Spark Streaming is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows.
What needs improvement with Apache Spark Streaming?
We don't have enough experience to be judgmental about its flaws, as we've only used stable features like batch micro-batch. Integration poses no problem; however, I don't use some features and can...
What is your primary use case for Apache Spark Streaming?
We use Spark Streaming in a micro-batch region. It's not a full real-time system, but it offers high performance and low latency.
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?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team. The lack of easy access to the Confluent support team is also a...
 

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: March 2025.
848,253 professionals have used our research since 2012.