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

Amazon Kinesis vs Apache Spark Streaming 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

Amazon Kinesis
Ranking in Streaming Analytics
12th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
29
Ranking in other categories
No ranking in other categories
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
 

Mindshare comparison

As of September 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 3.9%, down from 7.0% compared to the previous year. The mindshare of Apache Spark Streaming is 4.6%, up from 3.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Spark Streaming4.6%
Amazon Kinesis3.9%
Other91.5%
Streaming Analytics
 

Featured Reviews

reviewer1480695 - PeerSpot reviewer
Director of Software Development at a tech vendor with 10,001+ employees
Has enabled real-time processing of critical event streams with seamless cloud integration
We are contemplating moving away from Amazon Kinesis primarily because of the cost. It is very useful, but if we write our own analytics and data processing pipeline, it would be much cheaper for us. The cost is a primary hindrance. That's why we are not using it widely. For our critical pipeline we are using it, but after that we are putting it in an S3 bucket. Other pipelines directly put the events in an S3 bucket and then process from there. There is no lack of functions in Amazon Kinesis. Functionality-wise, we feel it's complete. The cost aspect is what we are really concerned about.
Kuldeep Pal - PeerSpot reviewer
Data Engineer at Walmart Global Tech
Efficient data handling empowers near-real-time fraud detection and robust recovery mechanisms
The positive impact from Apache Spark Streaming is its near real-time capability. It has a good ecosystem that provides good support. However, if you need purely real-time data, you would be going with Flink. Apache Spark Streaming is good for near-to-real-time data and requires less maintenance, which is beneficial for developers and companies. The new feature coming in Apache Spark Streaming 4 is continuous streaming. If continuous streaming becomes stable and performs comparably to Flink, then Apache Spark Streaming would be preferred everywhere due to its good maintenance and support system. While it is reliable, there are some issues with Apache Spark Streaming as it is not 100% reliable. Sometimes it fails, requiring numerous configurations such as checkpointing, watermarking, and other features. If you select a 10-minute window and the data arrives at the 30th minute, it sometimes loses data in between. You also have to apply back pressure when numerous messages are coming in. It requires constant monitoring and maintenance. I would say it is 90-95% reliable, but multiple configurations and frequent maintenance make it slightly less reliable. The continuous deployment feature being in beta phase could benefit everyone if released earlier.

Quotes from Members

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

Pros

"We have been able to drop our costs for ingesting data by about 60 to 70%."
"Kinesis replaced a whole tier of servers, so we didn't need to have a server to catch the data and then send the data somewhere else, because Kinesis was the input port for very large amounts of data."
"I find data Firehose and data streams are much more intelligent than other streaming solutions."
"The major advantage with Amazon Kinesis is the availability, additionally the reliability is awesome, the replay is incredibly fast, and the ingesting, buffering, and processing of data are really fast."
"With AWS, you don't have to invest in any kind of infrastructure."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"The Kinesis VideoStream and DataStream are the most important features."
"Amazon Kinesis's main purpose is to provide near real-time data streaming at a consistent 2Mbps rate, which is really impressive."
"The main benefits of Apache Spark Streaming include cost savings, time savings, and efficiency improvements about data storage."
"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."
"As an open-source solution, using it is basically free."
"The solution is better than average and some of the valuable features include efficiency and stability."
"With Apache Spark Streaming's integration with Anaconda and Miniconda with Python, I interact with databases using data frames or data sets in micro versions and create solutions based on business expectations for decision-making, logistic regression, linear regression, or machine learning which provides image or voice record and graphical data for improved accuracy."
"I appreciate Apache Spark Streaming's micro-batching capabilities; the watermarking functionality and related features are quite good."
"Apache Spark Streaming is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows."
"For Apache Spark Streaming, the feature I appreciated most is that it provides live data delivery; additionally, it provides the capability to send a larger amount of data in parallel."
 

Cons

"We are contemplating moving away from Amazon Kinesis primarily because of the cost."
"There could be valid data in Kinesis that is not being processed, which affects stability. Although it rarely happens, this issue has been observed in many deployments, making it not completely stable."
"The technical support could be improved. They tend to send you back to the documentation."
"In order to do a successful setup, the person handling the implementation needs to know the solution very well. You can't just come into it blind and with little to no experience."
"When we had some of those slow downs, we used AWS support and I can't say that we had a great experience and they resolved the issues, but they looked into some of the flow downs and ultimately we just decided there was nothing we could do."
"In general, the pain point for us was that once the data gets into Kinesis there is no way for us to understand what's happening because Kinesis divides everything into shards. So if we wanted to understand what's happening with a particular shard, whether it is published or not, we could not. Even with the logs, if we want to have some kind of logging it is in the shard."
"AI processing or cleaning up data would be nice since I don't think it is a feature in Amazon Kinesis right now."
"Amazon Kinesis involved a more complex setup and configuration than Azure Event Hub."
"It was resource-intensive, even for small-scale applications."
"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."
"Integrating event-level streaming capabilities could be beneficial."
"While it is reliable, there are some issues with Apache Spark Streaming as it is not 100% reliable."
"The initial setup is quite complex."
"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."
"The downside is when you have this the other way around in the columns, it becomes really hard to use."
"There could be an improvement in the area of the user configuration section, it should be less developer-focused and more business user-focused."
 

Pricing and Cost Advice

"The tool's pricing is cheap."
"Amazon Kinesis is an expensive solution."
"Under $1,000 per month."
"I think for us, with Amazon Kinesis, if we have to set up our own Kafka or cluster, it will be very time-consuming. If one considers the aforementioned aspect, Amazon Kinesis is a cheap tool."
"Amazon Kinesis pricing is sometimes reasonable and sometimes could be better, depending on the planning, so it's a five out of ten for me."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"The tool's entry price is cheap. However, pricing increases with data volume."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"People pay for Apache Spark Streaming as a service."
"Spark is an affordable solution, especially considering its open-source nature."
"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."
"I was using the open-source community version, which was self-hosted."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
913,076 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
9%
Manufacturing Company
8%
Outsourcing Company
7%
Financial Services Firm
14%
Outsourcing Company
13%
Comms Service Provider
10%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise10
Large Enterprise10
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise7
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon Kinesis?
Amazon Kinesis and Lambda pricing is competitive, but we noticed that scaling and large volumes could potentially increase costs significantly.
What needs improvement with Amazon Kinesis?
We are contemplating moving away from Amazon Kinesis primarily because of the cost. It is very useful, but if we write our own analytics and data processing pipeline, it would be much cheaper for u...
What is your primary use case for Amazon Kinesis?
We use Amazon Kinesis for stream processing. We get events from on-premise devices to the cloud. We get many device events and we have to process these events that are coming from the devices. To p...
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...
 

Also Known As

Amazon AWS Kinesis, AWS Kinesis, Kinesis
Spark Streaming
 

Overview

 

Sample Customers

Zillow, Netflix, Sonos
UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, eBay Inc.
Find out what your peers are saying about Amazon Kinesis vs. Apache Spark Streaming and other solutions. Updated: August 2026.
913,076 professionals have used our research since 2012.