We performed a comparison between AWS Database Migration Service and Confluent based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution is stable and reliable."
"The process is now simplified because there won't be maintenance. Usually we can take a snapshot of the number I need. We can automate the backup snapshots and we can restore it very quickly. We get many benefits from the application."
"What I like about AWS Database Migration Service is that it's a good product that allows you to migrate terabytes of data. My team was able to migrate almost 16TB of data using AWS Database Migration Service. The solution works fine for my use case."
"The product is cheaper than all platforms"
"Even if it does break down, it will automatically recover itself and resumes from where it stopped."
"If your infrastructure is already on Amazon, it simply makes the most sense to use a tool officially provided by them as an additional service, rather than having to rely on a third-party solution."
"The Schema Conversion Tool helps to covert the convertible objects and define the non-convertible objects"
"Scalable and stable solution for migrating databases to AWS, with valuable features such as parallel full load and continuous data replication."
"The solution can handle a high volume of data because it works and scales well."
"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."
"It is also good for knowledge base management."
"I would rate the scalability of the solution at eight out of ten. We have 20 people who use Confluent in our organization now, and we hope to increase usage in the future."
"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."
"The client APIs are the most valuable feature."
"The design of the product is extremely well built and it is highly configurable."
"The documentation process is fast with the tool."
"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."
"There are a set of complexities and challenges when a user wants to integrate AWS products with Microsoft products."
"Whatever solution worked today can not be reused in the next migration."
"We would like to see some improvement in the performance of large scale procedures, such as when we migrate from Oracle to csSQL."
"As a solution, the better thing is if more platforms come with direct compatibility, like connecting to different data sources. The basic problem I faced the most was while transferring and reading data from Excel. So, one time, I found that all the components I had declared in my scripts were able to take it. And after some patching happens, it is not able to support that. Again, we need to update the version of Excel. So, it's not like a plug-in type place where you have done the solution and are confident that it will work. So, this is an area of improvement."
"Support could be more expedient. Right now I am waiting on support for an extension."
"The performance of data migration could be smoother."
"The names of the services need improvement since AWS doesn't indicate what the function of the product is presently. You need to read a lot to find the service that you want in the product."
"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."
"They should remove Zookeeper because of security issues."
"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."
"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 be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"The formatting aspect within the page can be improved and more powerful."
"Confluent's price needs improvement."
More AWS Database Migration Service Pricing and Cost Advice →
AWS Database Migration Service is ranked 2nd in Cloud Data Integration with 27 reviews while Confluent is ranked 4th in Streaming Analytics with 21 reviews. AWS Database Migration Service is rated 7.8, while Confluent is rated 8.4. The top reviewer of AWS Database Migration Service writes "A cloud solution for live replication but has stability issues". On the other hand, the top reviewer of Confluent writes "Has good technical support services and a valuable feature for real-time data streaming ". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Qlik Replicate, Fivetran and Oracle GoldenGate Cloud Service, whereas Confluent is most compared with Amazon MSK, Amazon Kinesis, Databricks, AWS Glue and Azure Stream Analytics. See our AWS Database Migration Service vs. Confluent report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
