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

Amazon Kinesis vs Confluent comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 8, 2026

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
4th
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
6th
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 May 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 4.5%, down from 8.3% compared to the previous year. The mindshare of Confluent is 6.6%, down from 8.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis4.5%
Confluent6.6%
Other88.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.
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

"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."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"We have been able to drop our costs for ingesting data by about 60 to 70%."
"The scalability is pretty good."
"The integration between Amazon Kinesis and Lambda helps us significantly."
"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."
"One of the best features of Amazon Kinesis is the multi-partition."
"Amazon Kinesis's main purpose is to provide near real-time data streaming at a consistent 2Mbps rate, which is really impressive."
"With Confluent Cloud we no longer need to handle the infrastructure and the plumbing, which is a concern for Confluent, and the other advantage is that all portfolios have access to the data that is being shared."
"A person with a good IT background and HTML will not have any trouble with Confluent."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"The design of the product is extremely well built and it is highly configurable."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"Some of the best features are that it's very quick to set up, very easy to have a centralized area that gives us a history of changes, and the ability to give feedback on any information placed onto the pages."
"With Confluent Cloud we no longer need to handle the infrastructure and the plumbing, which is a concern for Confluent. The other advantage is that all portfolios have access to the data that is being shared."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
 

Cons

"In order to do a successful setup, the person handling the implementation needs to know the solution very well."
"The default limit that they have, which at the moment is 5,000 records per second seems too low."
"There are some kind of hard limits on Amazon Kinesis, and if you hit that, then you will get the throughput exceed error."
"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."
"Amazon Kinesis has a less meaningful and easy use than Azure Event Hub."
"We were charged high costs for the solution’s enhanced fan-out feature."
"Could include features that make it easier to scale."
"Amazon Kinesis could improve its pricing to be more competitive, especially for large volumes."
"Currently, in the early stages, I see a gap on the security side. If you are using the SaaS version, we would like to get a fuller, more secure solution that can be adopted right out of the box."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"One area we've identified that could be improved is the governance and access control to the Kafka topics. We've found some limitations, like a threshold of 10,000 rules per cluster, that make it challenging to manage access at scale if we have many different data sources."
"The product should integrate tools for incorporating diagrams like Lucidchart. It also needs to improve its formatting features. We also faced issues while granting permissions."
"The formatting aspect within the page can be improved and more powerful."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"It requires some application specific connectors which are lacking. This needs to be added."
 

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 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."
"The tool's entry price is cheap. However, pricing increases with data volume."
"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."
"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."
"Under $1,000 per month."
"The product falls on a bit of an expensive side."
"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 is highly priced."
"The solution is cheaper than other products."
"On a scale from one to ten, where one is low pricing and ten is high pricing, I would rate Confluent's pricing at five. I have not encountered any additional costs."
"It comes with a high cost."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"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."
"You have to pay additional for one or two features."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
7%
Construction Company
5%
Financial Services Firm
16%
Retailer
11%
Computer Software Company
10%
Manufacturing Company
5%
 

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 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 ...
What is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
 

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: April 2026.
893,221 professionals have used our research since 2012.