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

Amazon MSK vs Confluent comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 18, 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 MSK
Ranking in Streaming Analytics
12th
Average Rating
7.2
Reviews Sentiment
6.5
Number of Reviews
14
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
7th
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 August 2026, in the Streaming Analytics category, the mindshare of Amazon MSK is 3.9%, down from 6.5% compared to the previous year. The mindshare of Confluent is 6.4%, down from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.4%
Amazon MSK3.9%
Other89.7%
Streaming Analytics
 

Featured Reviews

SYED SHAAZ - PeerSpot reviewer
Co-Founder & CTO at Photios AI
Improved data streaming and integration challenges prompt search for alternatives
The integration capabilities of Amazon MSK are not very flexible. If you have your own self-managed Kafka, that helps significantly because you can set up configurations. We are considering self-managed Kafka since our product is only one year old. The Kafka integrations are fine, but the configurations are an issue. The only issue with Amazon MSK that we are facing is the configurations. There are preset configurations and limited configurations that we can set for our unique use case. The product could improve by allowing us to set different configurations. I would also like to see Amazon MSK improve in the area of connectors. We are considering Confluent Cloud because they have many more connectors. They have KSQL DB and governance features. It is slightly costlier, but Confluent offers more flexibility with their connectors.
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 scalability and usability are quite remarkable."
"Amazon MSK's separation of concerns and ease of creating and deploying new features are highly valuable. It just requires to assign them to the topic, and then anyone who needs to consume these messages can do so directly from Amazon MSK. This separation of concerns makes it very convenient, especially for new feature development, as developers can easily access the messages they need without having to deal with complex server communications or protocol setups."
"It provides installations, scaling, and other functionalities straight out of the box."
"Overall, it is very cost-effective based on the workflow."
"The most valuable feature of Amazon MSK is the integration."
"Amazon MSK has contributed positively to our real-time analytics capabilities because Fortis's dashboards have dashboard health that needs to be maintained, user logs that need to be maintained, and usage tracking."
"It offers good stability."
"Amazon MSK has good integration because our team has been undergoing significant changes. Coupling it with MSK within AWS is helpful. We don't have to set up additionals or monitor external environments. This"
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"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."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"The monitoring module is impressive."
"The design of the product is extremely well built and it is highly configurable."
"As an enterprise organization, data availability is critical and Confluent provides that SLA support."
"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

"The only issue with Amazon MSK that we are facing is the configurations. There are preset configurations and limited configurations that we can set for our unique use case."
"In my opinion, there are areas in Amazon MSK that could be improved, particularly in terms of configuration. Initially setting it up and getting it connected was quite challenging. The naming conventions for policies were updated by AWS, and some were undocumented, leading to confusion with outdated materials. It took us weeks of trial and error before discovering new methods through hidden tutorials and official documentation."
"We need to create connectors in Amazon MSK, but there are no default connectors in AWS for that purpose."
"It would be really helpful if Amazon MSK could provide a single installation that covers all the servers."
"Horizontal scale-out is actually not easy, making it an area where improvements are required."
"The cost of using Amazon MSK is high, which is a significant disadvantage, as the increase in cloud costs by 50% to 60% does not justify the savings."
"Amazon MSK could improve on the features they offer. They are still lagging behind Confluence."
"MSK should be easier to integrate with other solutions. It should be more flexible, integration-wise."
"I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team."
"The pricing was high for our needs. We should not have to pay for features we do not use."
"In Confluent, there could be a few more VPN options."
"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."
"It would be great if the knowledge based documents in the support portal could be available for public use as well."
"Confluent's price needs improvement."
"The beginner who doesn't know how to work on HTML will struggle as when you create spaces in the Confluent, if you want to have some meeting notes or anything else, you need to know HTML and which HTML tags to include."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
 

Pricing and Cost Advice

"When you create a complete enterprise-driven architecture that is deployable on an enterprise scale, I would say that the prices of Amazon MSK and Confluent Platform become comparable."
"The price of Amazon MSK is less than some competitor solutions, such as Confluence."
"The platform has better pricing than one of its competitors."
"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."
"You have to pay additional for one or two features."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"It comes with a high cost."
"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."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
908,402 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
10%
Computer Software Company
10%
Construction Company
8%
Financial Services Firm
15%
Retailer
12%
Computer Software Company
8%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise7
Large Enterprise5
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
 

Questions from the Community

What needs improvement with Amazon MSK?
The integration capabilities of Amazon MSK are not very flexible. If you have your own self-managed Kafka, that helps significantly because you can set up configurations. We are considering self-ma...
What is your primary use case for Amazon MSK?
We are recently working with Amazon MSK at Fortis, where we have multiple dashboards in our revenue intelligence platform. We are streaming data from different apps into those dashboards. The data ...
What advice do you have for others considering Amazon MSK?
We are working with Amazon MSK product, Managed Streaming for Apache Kafka. The main benefits I have seen from using Amazon MSK is that as a B2B enterprise client, we have many SLAs to fulfill. Tra...
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 Managed Streaming for Apache Kafka
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Amazon MSK vs. Confluent and other solutions. Updated: June 2026.
908,402 professionals have used our research since 2012.