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

Amazon Kinesis vs IBM Streams 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
11th
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
24th
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 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 IBM Streams is 2.2%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis4.0%
IBM Streams2.2%
Other93.8%
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

"One of the best features of Amazon Kinesis is the multi-partition."
"I find almost all features valuable, especially the timing and fast pace movement."
"Amazon Kinesis has improved our ROI."
"I like the ease of use and how we can quickly get the configurations done, making it pretty straightforward and stable."
"Great auto-scaling, auto-sharing, and auto-correction features."
"Amazon Kinesis also provides us with plenty of flexibility."
"The management and analytics are valuable features."
"I find data Firehose and data streams are much more intelligent than other streaming solutions."
"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."
"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."
"The product has enabled us to create solutions to client problems that would have either been impossible or very expensive/difficult using other technologies."
 

Cons

"We are contemplating moving away from Amazon Kinesis primarily because of the cost."
"Kinesis is good for Amazon Cloud but not as suitable for other cloud vendors."
"Amazon Kinesis could improve its pricing to be more competitive, especially for large volumes."
"If there were better documentation on optimal sharding strategies then it would be helpful."
"Amazon Kinesis involved a more complex setup and configuration than Azure Event Hub."
"Amazon Kinesis should improve its limits."
"The price is not much cheaper. So, there is room for improvement in the pricing."
"There are certain shortcomings in the machine learning capacity offered by the product, making it an area where improvements are required."
"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."
"We had some stability issues where we used embedded Zookeeper in production."
"The price and versatility of this product need to improve - it is not inexpensive."
"The development IDE sometimes crashes and freezes."
 

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 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."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"Amazon Kinesis is an expensive solution."
"The tool's pricing is cheap."
"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."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
910,454 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
10%
Manufacturing Company
8%
Construction Company
6%
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.
910,454 professionals have used our research since 2012.