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
7th
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 October 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 3.8%, down from 6.6% 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.8%
Other91.6%
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.
Himansu Jena - PeerSpot reviewer
Sr Project Manager at Raj Subhatech
Efficient real-time data management and analysis with advanced features
There are various ways we can improve Apache Spark Streaming through best practices. The initial part requires attention to batch interval tuning, which helps small intervals in micro batches based on latency requirements and helps prevent back pressure. We can use data formats such as Parquet or ORC for storage that needs faster reads and leveraging feature predicate push-down optimizations. We can implement serialization which helps with any Kyro in terms of .NET or Java. We have boxing and unboxing serialization for XML and JSON for converting key-pair values stored in browser. We can also implement caching mechanisms for storing and recomputing multiple operations. We can use specified joins which help with smaller databases, and distributed joins can minimize users. We can implement project optimization memory for CPU efficiency, known as Tungsten. Additionally, load balancing, checkpointing, and schema evaluation are areas to consider based on performance and bottlenecks. We can use Bugzilla tools for tracking and Splunk to monitor the performance of process systems, utilization, and performance based on data frames or data sets.

Quotes from Members

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

Pros

"I have worked in companies that build tools in-house. They face scaling challenges."
"Its scalability is very high. There is no maintenance and there is no throughput latency. I think data scalability is high, too. You can ingest gigabytes of data within seconds or milliseconds."
"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."
"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."
"I like the ease of use and how we can quickly get the configurations done, making it pretty straightforward and stable."
"The product's initial setup phase is not difficult because we are using the tool on the cloud."
"The solution works well in rather sizable environments."
"Amazon Kinesis is easy to get started with, provides good documentation, and has a multilang daemon interface that makes it programming-language agnostic."
"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."
"The solution is better than average and some of the valuable features include efficiency and stability."
"It's the fastest solution on the market with low latency data on data transformations."
"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."
"I appreciate Apache Spark Streaming's micro-batching capabilities; the watermarking functionality and related features are quite good."
"Apache Spark's capabilities for machine learning are quite extensive and can be used in a low-code way."
"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."
"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."
 

Cons

"Amazon Kinesis could improve its pricing to be more competitive, especially for large volumes."
"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."
"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."
"The default limit that they have, which at the moment is 5,000 records per second seems too low."
"We were charged high costs for the solution’s enhanced fan-out feature."
"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."
"The solution has a two-minute maximum time delay for live streaming, which could be reduced."
"There are some kind of hard limits on Amazon Kinesis, and if you hit that, then you will get the throughput exceed error."
"In terms of improvement, the UI could be better."
"The debugging aspect could use some improvement."
"We don't have enough experience to be judgmental about its flaws."
"One improvement I would expect is real-time processing instead of micro-batch or near real-time."
"It was resource-intensive, even for small-scale applications."
"While it is reliable, there are some issues with Apache Spark Streaming as it is not 100% reliable."
"Integrating event-level streaming capabilities could be beneficial."
"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 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."
"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."
"The product falls on a bit of an expensive side."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"Under $1,000 per month."
"The tool's entry price is cheap. However, pricing increases with data volume."
"People pay for Apache Spark Streaming as a service."
"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."
"Spark is an affordable solution, especially considering its open-source nature."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
919,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
9%
Outsourcing Company
7%
University
7%
Financial Services Firm
15%
Outsourcing Company
14%
Comms Service Provider
8%
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: September 2026.
919,894 professionals have used our research since 2012.