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

AWS Database Migration Service vs Confluent comparison

 

Comparison Buyer's Guide

Executive Summary

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

AWS Database Migration Service
Average Rating
8.0
Reviews Sentiment
6.4
Number of Reviews
35
Ranking in other categories
Cloud Data Integration (2nd)
Confluent
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
Streaming Analytics (7th)
 

Featured Reviews

AG
Delivery Head Data Engineering at BAGIC
Streamlines data migration across platforms with cost-effective and scalable solutions
We have the continuous data integration feature, but it does not work very well in our given ecosystem because we have huge data volume, and it reads from archive log rather than the redo sequence. That is where it lacks, so we are not able to do continuous streaming data injection. The ability to handle heterogeneous migrations for our organization is adequate. I do not see a major value add, or see it as a marquee feature. It is a good tool, but we do not have that sort of uses requirement. In my 10 plus years of experience, I do not see that kind of requirement where I have to replicate it in real time. I leverage AWS CloudWatch for addressing migration issues. The major challenges come across CDC. We have created latency filter and everything, but there is no way to control it. Due to the nature of our business, the transactions increase during month end and year end. My transactions are supposed to increase, my workloads on my core system increases, but my DMS is not able to keep up with them, even if I increase it to a higher side. Improvements could be made in AWS Database Migration Service. Because of that, I am moving out of DMS now to a STRIIM solution. DMS works within AWS ecosystem, but they also have to look for third party solutions. Now Snowflake is a bigger player, or Databricks. Something that could be possible as a connector, whether paid or free, but giving as a connector to that ecosystem as well.
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 initial setup is very simple and straightforward."
"The most valuable feature is its ability to get all the changes in our data and store that in an S3 bucket."
"The most valuable feature of AWS Database Migration Service is it catches all the history changes, such as inset, observe, and delete. It tracks everything."
"AWS Database Migration Service is affordable and cheaper."
"I was very impressed by the scalability of AWS Database Migration Service."
"It's pretty useful when we need to migrate something big from a different type of database that AWS Data Migration Services supports."
"This efficient workflow has been particularly helpful."
"From my point of view, it was the best option in this case."
"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."
"Their tech support is amazing; they are very good, both on and off-site."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"Overall, it's a great company and they have excellent software."
"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."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
 

Cons

"This solution is compatible with only AWS."
"Improvements could be made in AWS Database Migration Service. Because of that, I am moving out of DMS now to a STRIIM solution."
"One area that AWS DMS can improve on is its conversion of data types. For example, in Oracle, you have a data type called RAW, but in PostgreSQL there is no such thing. Thus, AWS DMS doesn't know what type I want to use when migrating from Oracle to PostgreSQL, and when performing the migration, AWS DMS changed the RAW data type to the byte data type, which isn't what I wanted."
"What needs improvement in AWS Database Migration Service is that it lacks a log file validation feature. If the solution could provide more details about a particular transaction, that would be helpful. The stability of AWS Database Migration Service for online CDC records also needs to be improved."
"One drawback I experienced was with balance and sync."
"Migrating from here and pushing the data from on-premise to AWS cloud is a big challenge and a few more services from AWS would be helpful. For example, we are currently using ILDB internet tools which move data from on-premise to the AWS cloud. A few more services would be really helpful for me to move the master data."
"Years ago, the price was nominal and acceptable for the client to do a migration. Now, prices are challenging, especially with versions continually changing."
"The initial setup can be difficult for beginners in AWS Database Migration Service. You will need the training to complete it."
"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 formatting aspect within the page can be improved and more powerful."
"It would be great 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."
"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."
"There is a limitation when it comes to seamlessly importing Microsoft documents into Confluent pages, which can be inconvenient for users who frequently work with Microsoft Office tools and need to transition their content to Confluent."
"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."
"There is no local support team in Saudi Arabia."
 

Pricing and Cost Advice

"AWS Database Migration Service is the least expensive solution, but is still expensive."
"I would rate the pricing a seven out of ten."
"Cost is the only factor that is challenging."
"In terms of pricing, I'd rate it an eight out of ten, considering it's a well-priced solution."
"Pricing can be improved."
"The pricing is on the higher side."
"AWS Database Migration Service is very inexpensive."
"For Egypt, the product's prices are high, making it a specific problem in one region and not globally."
"You have to pay additional for one or two features."
"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."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Confluent is an expensive solution."
"Confluent is highly priced."
"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."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
7%
Manufacturing Company
6%
Outsourcing Company
5%
Financial Services Firm
15%
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 Enterprise9
Large Enterprise17
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
 

Questions from the Community

What resources can you use to learn how to utilize AWS Database Migration Service?
As with all AWS products, you are given very useful documentation with AWS Database Migration Service. Before we started using this product, we went over it and we were able to learn the basics an...
Would you recommend AWS Database Migration Service as a cloud data integration tool?
My current company started using AWS Database Migration Service upon my recommendation, and I continue telling people how good of a product it is. However, users should keep in mind a few things. ...
Is AWS Database Migration Service an affordable solution?
Compared to similar solutions, AWS Database Migration Service falls somewhere in the middle price-wise, at least from my experience. This being said, it is not a very affordable solution, especial...
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...
 

Also Known As

AWS Data Migration Service
No data available
 

Overview

 

Sample Customers

Veoci, Trimble, Nasdaq, shaadi.com, Hotelbeds, SysAid, Verizon, Expedia, Pega
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: June 2026.
902,988 professionals have used our research since 2012.