Try our new research platform with insights from 80,000+ expert users

Amazon Kinesis vs Confluent comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 2, 2025

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
2nd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
29
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
5th
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 5.4%, down from 9.0% compared to the previous year. The mindshare of Confluent is 6.8%, down from 8.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Amazon Kinesis5.4%
Confluent6.8%
Other87.8%
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.
PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.

Quotes from Members

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

Pros

"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 integration capabilities of the product are good."
"The solution works well in rather sizable environments."
"One of the best features of Amazon Kinesis is the multi-partition."
"What turns out to be most valuable is its integration with Lambda functions because you can process the data as it comes in. As soon as data comes, you'll fire a Lambda function to process a trench of data."
"The scalability is pretty good."
"The feature that I've found most valuable is the replay. That is one of the most valuable in our business. We are business-to-business so replay was an important feature - being able to replay for 24 hours. That's an important feature."
"The product's initial setup phase is not difficult because we are using the tool on the cloud."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"The benefit is escaping email communication. Sometimes people ignore emails or put them into spam, but with Confluence, everyone sees the same text at the same time."
"The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"Confluence's greatest asset is its user-friendly interface, coupled with its remarkable ability to seamlessly integrate with a vast range of other solutions."
"The solution can handle a high volume of data because it works and scales well."
"I would rate the scalability of the solution at eight out of ten. We have 20 people who use Confluent in our organization now, and we hope to increase usage in the future."
 

Cons

"There are certain shortcomings in the machine learning capacity offered by the product, making it an area where improvements are required."
"I suggest integrating additional features, such as incorporating Amazon Pinpoint or Amazon Connect as bundled offerings, rather than deploying them as separate services."
"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."
"Amazon Kinesis could improve its pricing to be more competitive, especially for large volumes."
"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."
"We are contemplating moving away from Amazon Kinesis primarily because of the cost."
"There could be valid data in Kinesis that is not being processed, which affects stability. Although it rarely happens, this issue has been observed in many deployments, making it not completely stable."
"It would be beneficial if Amazon Kinesis provided document based support on the internet to be able to read the data from the Kinesis site."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"We continuously face issues, such as Kafka being down and slow responses from the support team."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"The pricing model should include the ability to pick features and be charged for them only."
"The Schema Registry service could be improved. I would like a bigger knowledge base of other use cases and more technical forums. It would be good to have more flexible monitoring features added to the next release as well."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
 

Pricing and Cost Advice

"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 pricing is sometimes reasonable and sometimes could be better, depending on the planning, so it's a five out of ten for me."
"The fee is based on the number of hours the service is running."
"The solution's pricing is fair."
"Amazon Kinesis is an expensive solution."
"The tool's pricing is cheap."
"The tool's entry price is cheap. However, pricing increases with data volume."
"Under $1,000 per month."
"It comes with a high cost."
"You have to pay additional for one or two features."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Confluent is an expensive solution."
"Confluence's pricing is quite reasonable, with a cost of around $10 per user that decreases as the number of users increases. Additionally, it's worth noting that for teams of up to 10 users, the solution is completely free."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"The pricing model of Confluent could improve because if you have a classic use case where you're going to use all the features there is no plan to reduce the features. You should be able to pick and choose basic services at a reduced price. The pricing was high for our needs. We should not have to pay for features we do not use."
"The solution is cheaper than other products."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
881,665 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
14%
Manufacturing Company
6%
Comms Service Provider
5%
Financial Services Firm
16%
Computer Software Company
11%
Retailer
9%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise10
Large Enterprise9
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise16
 

Questions from the Community

What do you like most about Amazon Kinesis?
Amazon Kinesis's main purpose is to provide near real-time data streaming at a consistent 2Mbps rate, which is really impressive.
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 do you like most about Confluent?
I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and to...
What is your experience regarding pricing and costs for Confluent?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
 

Comparisons

 

Also Known As

Amazon AWS Kinesis, AWS Kinesis, Kinesis
No data available
 

Overview

 

Sample Customers

Zillow, Netflix, Sonos
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Amazon Kinesis vs. Confluent and other solutions. Updated: December 2025.
881,665 professionals have used our research since 2012.