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

Amazon Kinesis vs Apache Spark Streaming comparison

 

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
5th
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
10th
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 June 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 4.2%, down from 7.9% compared to the previous year. The mindshare of Apache Spark Streaming is 4.6%, up from 2.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis4.2%
Apache Spark Streaming4.6%
Other91.2%
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

"We have seen a return on our investment with Amazon Kinesis, as we are able to process data without any issue and it is our solution for ingesting data in other databases, such as Snowflake."
"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."
"The product's initial setup phase is not difficult because we are using the tool on the cloud."
"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 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."
"Great auto-scaling, auto-sharing, and auto-correction features."
"With AWS, you don't have to invest in any kind of infrastructure."
"I like the ease of use and how we can quickly get the configurations done, making it pretty straightforward and stable."
"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 is versatile. You can use it for competitive intelligence, gathering data from competitors, or for internal tasks like monitoring workflows."
"It is the most scalable tool that I have seen before."
"Apache Spark Streaming's most valuable feature is near real-time analytics. The developers can build APIs easily for a code-steaming pipeline. The solutions have an ecosystem of integration with other stock services."
"Apache Spark Streaming has features like checkpointing and Streaming API that are useful."
"The main benefits of Apache Spark Streaming include cost savings, time savings, and efficiency improvements about data storage."
"Spark Streaming is critical, quite stable, full-featured, and scalable."
"The solution is better than average and some of the valuable features include efficiency and stability."
 

Cons

"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."
"Amazon Kinesis has a less meaningful and easy use than Azure Event Hub."
"The tool should focus on having an alert system rather than having to use a third-party solution."
"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."
"There are certain shortcomings in the machine learning capacity offered by the product, making it an area where improvements are required."
"Amazon Kinesis involved a more complex setup and configuration than Azure Event Hub."
"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."
"There could be an improvement in the area of the user configuration section, it should be less developer-focused and more business user-focused."
"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 downside is when you have this the other way around in the columns, it becomes really hard to use."
"It was resource-intensive, even for small-scale applications."
"One improvement I would expect is real-time processing instead of micro-batch or near real-time."
"Integrating event-level streaming capabilities could be beneficial."
"In terms of improvement, the UI could be better."
"The solution itself could be easier to use."
 

Pricing and Cost Advice

"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."
"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."
"Amazon Kinesis is an expensive solution."
"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."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"The solution's pricing is fair."
"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."
"People pay for Apache Spark Streaming as a service."
"Spark is an affordable solution, especially considering its open-source nature."
"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.
902,456 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
12%
Manufacturing Company
8%
Construction Company
6%
Financial Services Firm
19%
Outsourcing Company
8%
Computer Software Company
8%
Comms Service Provider
8%
 

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: June 2026.
902,456 professionals have used our research since 2012.