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

Amazon Kinesis vs IBM Streams 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
IBM Streams
Ranking in Streaming Analytics
23rd
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
5
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 IBM Streams is 2.1%, up from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis3.9%
IBM Streams2.1%
Other94.0%
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.
Ahmed_Emad - PeerSpot reviewer
Territory Sales Leader at Sumerge
A solution for data pipelines but has connector limitations
We have used Kafka for seven years. IBM streams gives you many OOTB features that can boost the time-to-market, especially when it comes to reporting and monitoring for example. Confluent is recognized as one of the leaders in this space and the main reason for this is related to the complete vision of the platform also the large number of connectors. This gives the edge and competitive advatnage.

Quotes from Members

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

Pros

"The solution has the capacity to store the data anywhere from one day to a week and provides limitless storage for us."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"The scalability is pretty good."
"What I like about Amazon Kinesis is that it's very effective for small businesses. It's a well-managed solution with excellent reporting. Amazon Kinesis is also easy to use, and even a novice developer can work with it, versus Apache Kafka, which requires expertise."
"Everything is hosted and simple."
"Great auto-scaling, auto-sharing, and auto-correction features."
"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 solution works well in rather sizable environments."
"The OEM Solution (Excel-medical.com) running on top of IBM Streams provides real-time clinical algorithms that can give better insight into the patient's acuity, thus cutting off time to discharge patients and inversely making sure that sick patients don't get discharged until ready."
"The product has enabled us to create solutions to client problems that would have either been impossible or very expensive/difficult using other technologies."
"Easy development and deployment, Java implementation features, and the real time analyser and alarm function are the most valuable features for us."
"As a result, the TELCO company was able to cut down the time it took to respond to customer needs and there were fewer complaints."
 

Cons

"We are contemplating moving away from Amazon Kinesis primarily because of the cost."
"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."
"I suggest integrating additional features, such as incorporating Amazon Pinpoint or Amazon Connect as bundled offerings, rather than deploying them as separate services."
"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."
"Could include features that make it easier to scale."
"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."
"Kinesis Data Analytics needs to be improved somewhat. It's SQL based data but it is not as user friendly as MySQL or Athena tools."
"The development IDE sometimes crashes and freezes."
"The price and versatility of this product need to improve - it is not inexpensive."
"We had some stability issues where we used embedded Zookeeper in production."
"I’d like to see a tool kit specifically targeted at incremental machine learning. It’s already great for scoring previously trained models, but dynamically updating models is currently more of a 'grow your own' kind of thing."
 

Pricing and Cost Advice

"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."
"Amazon Kinesis is an expensive solution."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"The product falls on a bit of an expensive side."
"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 solution's pricing is fair."
"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."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
913,422 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
10%
Manufacturing Company
7%
Outsourcing Company
7%
Government
18%
Financial Services Firm
14%
Construction Company
14%
Comms Service Provider
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise10
Large Enterprise10
No data available
 

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...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Amazon AWS Kinesis, AWS Kinesis, Kinesis
IBM InfoSphere Streams
 

Overview

 

Sample Customers

Zillow, Netflix, Sonos
Globo TV, All England Lawn Tennis Club, CenterPoint Energy, Consolidated Communications Holdings, Darwin Ecosystem, Emory University Hospital, ICICI Securities, Irish Centre for Fetal and Neonatal Translational Research (INFANT), Living Roads, Mobileum, Optibus, Southern Ontario Smart Computing Innovation Platform (SOSCIP), University of Alberta, University of Montana, University of Ontario Institute of Technology, Wimbledon 2015
Find out what your peers are saying about Amazon Kinesis vs. IBM Streams and other solutions. Updated: August 2026.
913,422 professionals have used our research since 2012.