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
11th
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
9th
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 August 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 4.0%, down from 7.6% compared to the previous year. The mindshare of Apache Spark Streaming is 4.7%, up from 3.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Spark Streaming4.7%
Amazon Kinesis4.0%
Other91.3%
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 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."
"The integration between Amazon Kinesis and Lambda helps us significantly."
"The integration capabilities of the product are good."
"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."
"The scalability is pretty good, as one can have any number of nodes spawned or replicated on the primary so that any load can be handled, perhaps a few terabytes with ease in around 15 seconds."
"The product's initial setup phase is not difficult because we are using the tool on the cloud."
"Before Data Streams, we were using a couple of other solutions, including Talend and Pentaho, to move data around, and the ability to have one single flow of data from multiple consumers simplified our architecture a lot, saves us a lot of time, and will help us in the future when we have to build additional applications based on the same input data."
"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."
"Spark Streaming is critical, quite stable, full-featured, and scalable."
"As an open-source solution, using it is basically free."
"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 main benefits of Apache Spark Streaming include cost savings, time savings, and efficiency improvements about data storage."
"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."
"Apache Spark's capabilities for machine learning are quite extensive and can be used in a low-code way."
"It is the most scalable tool that I have seen before."
 

Cons

"Could include features that make it easier to scale."
"The default limit that they have, which at the moment is 5,000 records per second seems too low."
"The tool should focus on having an alert system rather than having to use a third-party solution."
"We were charged high costs for the solution’s enhanced fan-out feature."
"AI processing or cleaning up data would be nice since I don't think it is a feature in Amazon Kinesis right now."
"For me, especially with video streams, there's sometimes a kind of delay when the data has to be pumped to other services. This delay could be improved in Kinesis, or especially the Kinesis Video Streams, which is being used for different use cases for Amazon Connect. With that improvement, a lot of other use cases of Amazon Connect integrating with third-party analytic tools would be easier."
"Kinesis is good for Amazon Cloud but not as suitable for other cloud vendors."
"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."
"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 debugging aspect could use some improvement."
"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 initial setup is quite complex."
"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."
"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."
"We would like to have the ability to do arbitrary stateful functions in Python."
 

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 fee is based on the number of hours the service is running."
"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."
"The solution's pricing is fair."
"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."
"The product falls on a bit of an expensive side."
"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."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"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."
"I was using the open-source community version, which was self-hosted."
"People pay for Apache Spark Streaming as a service."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
911,493 professionals have used our research since 2012.
 

Top Industries

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