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 integration between Amazon Kinesis and Lambda helps us significantly."
"One of the best features of Amazon Kinesis is the multi-partition."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"We have been able to drop our costs for ingesting data by about 60 to 70%."
"The most valuable feature is that it has a pretty robust way of capturing things."
"Amazon Kinesis also provides us with plenty of flexibility."
"From my experience, one of the most valuable features is the ability to track silent events on endpoints. Previously, these events might have gone unnoticed, but now we can access them within the product range. For example, if a customer reports that their calls are not reaching the portal files, we can use this feature to troubleshoot and optimize the system."
"The solution has the capacity to store the data anywhere from one day to a week and provides limitless storage for us."
"It is the most scalable tool that I have seen before."
"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."
"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 was straightforward in terms of maintenance. It was actively developed, and migrating from an older to a newer version was quite simple."
"Apache Spark Streaming has features like checkpointing and Streaming API that are useful."
"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."
"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."
"Apache Spark Streaming is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows."
 

Cons

"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."
"Something else to mention is that we use Kinesis with Lambda a lot and the fact that you can only connect one Stream to one Lambda, I find is a limiting factor. I would definitely recommend to remove that constraint."
"Amazon Kinesis involved a more complex setup and configuration than Azure Event Hub."
"If there were better documentation on optimal sharding strategies then it would be helpful."
"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."
"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 solution has a two-minute maximum time delay for live streaming, which could be reduced."
"I think the default settings are far too low."
"The downside is when you have this the other way around in the columns, it becomes really hard to use."
"The cost and load-related optimizations are areas where the tool lacks and needs improvement."
"Integrating event-level streaming capabilities could be beneficial."
"It was resource-intensive, even for small-scale applications."
"We don't have enough experience to be judgmental about its flaws."
"The initial setup is quite complex."
"In terms of improvement, the UI could be better."
"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."
 

Pricing and Cost Advice

"Amazon Kinesis is an expensive solution."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"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."
"In general, cloud services are very convenient to use, even if we have to pay a bit more, as we know what we are paying for and can focus on other tasks."
"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."
"The product falls on a bit of an expensive side."
"Under $1,000 per month."
"The pricing depends on the use cases and the level of usage. If you wanted to use Kinesis for different use cases, there's definitely a cheaper base cost involved. However, it's not entirely cheap, as different use cases might require different levels of Kinesis usage."
"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.
912,069 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,069 professionals have used our research since 2012.