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
8th
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 November 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 3.9%, down from 6.4% compared to the previous year. The mindshare of IBM Streams is 2.2%, up from 1.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis3.9%
IBM Streams2.2%
Other93.9%
Streaming Analytics
 

Featured Reviews

CD
AWS Cloud Architect at a healthcare company with 10,001+ employees
Real-time streaming and seamless integration enhance workloads with room for competitive pricing improvements
Amazon Kinesis is easy to get started with, provides good documentation, and has a multilang daemon interface that makes it programming-language agnostic. The throughput is convenient for processing volumes out of the box and does not require complex configurations. It also provides auto-scaling with different partition keys into various shards. Lambda's scalability, seamless integration with other AWS services, and support for multiple programming languages are very beneficial.
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 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."
"Compared to what we were doing with Kafka, which was taking about 30% just to keep things together, with Kinesis I think we're probably saving tens of thousands, if not $100,000 per year."
"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."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"The most valuable feature is that it has a pretty robust way of capturing things."
"Amazon Kinesis has improved our ROI."
"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 management and analytics are valuable features."
"The product has enabled us to create solutions to client problems that would have either been impossible or very expensive/difficult using other technologies."
"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."
"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."
"Easy development and deployment, Java implementation features, and the real time analyser and alarm function are the most valuable features for us."
 

Cons

"Lacks first in, first out queuing."
"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 services which are described in the documentation could use some visual presentation because for someone who is new to the solution the documentation is not easy to follow or beginner friendly and can leave a person feeling helpless."
"In order to do a successful setup, the person handling the implementation needs to know the solution very well. You can't just come into it blind and with little to no experience."
"If there were better documentation on optimal sharding strategies then it would be helpful."
"The tool should focus on having an alert system rather than having to use a third-party solution."
"Amazon Kinesis should improve its limits."
"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."
"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."
"The development IDE sometimes crashes and freezes."
"The price and versatility of this product need to improve - it is not inexpensive."
 

Pricing and Cost Advice

"The solution's pricing is fair."
"The product falls on a bit of an expensive side."
"The tool's entry price is cheap. However, pricing increases with data volume."
"The fee is based on the number of hours the service is running."
"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."
"Amazon Kinesis is an expensive solution."
"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."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
920,769 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%
Government
16%
Financial Services Firm
15%
Construction Company
13%
Comms Service Provider
11%
 

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: September 2026.
920,769 professionals have used our research since 2012.