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

"The most valuable feature is that it has a pretty robust way of capturing things."
"I like the ease of use and how we can quickly get the configurations done, making it pretty straightforward and stable."
"Kinesis is a fully managed program streaming application. You can manage any infrastructure. It is also scalable. Kinesis can handle any amount of data streaming and process data from hundreds, thousands of processes in every source with very low latency."
"We have been able to drop our costs for ingesting data by about 60 to 70%."
"The integration between Amazon Kinesis and Lambda helps us significantly."
"There is no problem with the tool's stability."
"The solution's technical support is flawless."
"I find almost all features valuable, especially the timing and fast pace movement."
"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."
"The solution is better than average and some of the valuable features include efficiency and stability."
"The main benefits of Apache Spark Streaming include cost savings, time savings, and efficiency improvements about data storage."
"It's the fastest solution on the market with low latency data on data transformations."
"Apache Spark Streaming was straightforward in terms of maintenance. It was actively developed, and migrating from an older to a newer version was quite simple."
"The solution is very stable and reliable."
"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."
"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."
 

Cons

"One area for improvement in the solution is the file size limitation of 10 Mb. My company works with files with a larger file size. The batch size and throughput also need improvement in Amazon Kinesis."
"It would be beneficial if Amazon Kinesis provided document based support on the internet to be able to read the data from the Kinesis site."
"The default limit that they have, which at the moment is 5,000 records per second seems too low."
"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."
"One thing that would be nice would be a policy for increasing the number of Kinesis streams because that's the one thing that's constant. You can change it in real time, but somebody has to change it, or you have to set some kind of meter. So, auto-scaling of adding and removing streams would be nice."
"AI processing or cleaning up data would be nice since I don't think it is a feature in Amazon Kinesis right now."
"We are contemplating moving away from Amazon Kinesis primarily because of the cost."
"Amazon Kinesis could improve its pricing to be more competitive, especially for large volumes."
"While it is reliable, there are some issues with Apache Spark Streaming as it is not 100% reliable."
"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."
"There could be an improvement in the area of the user configuration section, it should be less developer-focused and more business user-focused."
"The downside is when you have this the other way around in the columns, it becomes really hard to use."
"In terms of improvement, the UI could be better."
"One improvement I would expect is real-time processing instead of micro-batch or near real-time."
"When dealing with various data types including COBOL, Excel, JSON, video, audio, and MPG files, challenges can arise with incomplete or missing values."
"The debugging aspect could use some improvement."
 

Pricing and Cost Advice

"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"The product falls on a bit of an expensive side."
"Under $1,000 per month."
"The fee is based on the number of hours the service is running."
"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 is an expensive solution."
"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."
"Spark is an affordable solution, especially considering its open-source nature."
"I was using the open-source community version, which was self-hosted."
"People pay for Apache Spark Streaming as a service."
"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."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
912,022 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
10%
Manufacturing Company
7%
Outsourcing Company
6%
Financial Services Firm
15%
Comms Service Provider
10%
Outsourcing Company
10%
Construction 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.
912,022 professionals have used our research since 2012.