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

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
6th
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
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 January 2026, in the Streaming Analytics category, the mindshare of Amazon MSK is 5.1%, down from 8.4% compared to the previous year. The mindshare of Confluent is 6.8%, down from 8.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Confluent6.8%
Amazon MSK5.1%
Other88.1%
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

"Amazon MSK has significantly improved our organization by building seamless integration between systems."
"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 is a stable product."
"It provides installations, scaling, and other functionalities straight out of the box."
"The solution's technical support was helpful."
"The scalability and usability are quite remarkable."
"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."
"Amazon MSK's scalability is very good."
"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."
"A person with a good IT background and HTML will not have any trouble with Confluent."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"The design of the product is extremely well built and it is highly configurable."
"The most valuable feature that we are using is the data replication between the data centers allowing us to configure a disaster recovery or software. However, is it's not mandatory to use and because most of the features that we use are from Apache Kafka, such as end-to-end encryption. Internally, we can develop our own kind of product or service from Apache Kafka."
 

Cons

"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."
"The product's schema support needs enhancement. It will help enhance integration with many kinds of languages of programming languages, especially for environments using languages like .NET."
"Horizontal scale-out is actually not easy, making it an area where improvements are required."
"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."
"The configuration seems a little complex and the documentation on the product is not available."
"It should be more flexible, integration-wise."
"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."
"The downside of Amazon MSK is that when I needed to make a small change in the MSK configuration, it wasn't possible. I had to remove and drop all the clusters and recreate them again, which is complicated in a production environment."
"Confluent has a good monitoring tool, but it's not customizable."
"there is room for improvement in the visualization."
"I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"The formatting aspect within the page can be improved and more powerful."
"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 would help if the knowledge based documents in the support portal could be available for public use as well."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
 

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."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"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."
"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 is highly priced."
"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."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
881,114 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
12%
Manufacturing Company
6%
Construction Company
4%
Financial Services Firm
17%
Computer Software Company
11%
Retailer
9%
Manufacturing Company
7%
 

Company Size

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

Questions from the Community

What do you like most about Amazon MSK?
Amazon MSK has significantly improved our organization by building seamless integration between systems.
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 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 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: December 2025.
881,114 professionals have used our research since 2012.