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
5th
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
9th
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 June 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 4.2%, down from 7.9% compared to the previous year. The mindshare of Confluent is 6.6%, down from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis4.2%
Confluent6.6%
Other89.2%
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.
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 most valuable feature of Amazon Kinesis is real-time data streaming."
"From my experience, one of the most valuable features is the ability to track silent events on endpoints. Previously, these events might have gone unnoticed, but now we can access them within the product range. For example, if a customer reports that their calls are not reaching the portal files, we can use this feature to troubleshoot and optimize the system."
"The solution's technical support is flawless."
"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."
"I like the ease of use and how we can quickly get the configurations done, making it pretty straightforward and stable."
"I find data Firehose and data streams are much more intelligent than other streaming solutions."
"Amazon Kinesis also provides us with plenty of flexibility."
"Great auto-scaling, auto-sharing, and auto-correction features."
"The design of the product is extremely well built and it is highly configurable."
"The documentation process is fast with the tool."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"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."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"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."
 

Cons

"We were charged high costs for the solution’s enhanced fan-out feature."
"For me, especially with video streams, there's sometimes a kind of delay when the data has to be pumped to other services. This delay could be improved in Kinesis, or especially the Kinesis Video Streams, which is being used for different use cases for Amazon Connect. With that improvement, a lot of other use cases of Amazon Connect integrating with third-party analytic tools would be easier."
"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 tool should focus on having an alert system rather than having to use a third-party solution."
"The default limit that they have, which at the moment is 5,000 records per second seems too low."
"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."
"If there were better documentation on optimal sharding strategies then it would be helpful."
"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."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team."
"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. Confluence could do a better job sharing best practices or a reusable pattern that others have used, especially for companies that can not afford to hire professional services from Confluent."
"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."
"It could have more themes. They should also have more reporting-oriented plugins as well. It would be great to have free custom reports that can be dispatched directly from Jira."
"It could have more integration with different platforms."
"Confluent's price needs improvement."
 

Pricing and Cost Advice

"The product falls on a bit of an expensive side."
"Amazon Kinesis is an expensive solution."
"The tool's pricing is cheap."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"The solution's pricing is fair."
"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."
"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."
"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."
"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."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"Confluent is highly priced."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Confluent is an expensive solution."
"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.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
12%
Manufacturing Company
8%
Construction Company
5%
Financial Services Firm
16%
Retailer
11%
Computer Software Company
8%
Manufacturing Company
6%
 

Company Size

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

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...
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: June 2026.
900,747 professionals have used our research since 2012.