We performed a comparison between AWS Database Migration Service and Talend Data integration 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 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 good for smaller workloads and provides compatibility."
"The tools are very user-friendly."
"Support is helpful."
"Scalable and stable solution for migrating databases to AWS, with valuable features such as parallel full load and continuous data replication."
"It's pretty useful when we need to migrate something big from a different type of database that AWS Data Migration Services supports."
"The initial setup is very straightforward."
"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."
"I'm very passionate about this solution because if you look at any other tool that costs around $200 - $300,000, like Delphix which costs you a million dollars, Talend is very cheap and is almost is at par with what others can do. There is one thing which Delphix does which Talend cannot do, but overall, I would say apart from that, if you're looking for a solution, you should give it a try."
"The product's integration with PostgreSQL and Jira has been helpful for us. Its performance is good. However, we do not use it for large data sets."
"Talend Data integration has a wide library of connectors."
"Talend's most valuable feature is its ability to generate code and packages efficiently."
"We have multiple use cases for this solution. We integrate with Salesforce, SAP and Oracle databases to build business logic and provide reporting."
"This solution can offer more tweaks where the latency can be brought down to fifteen seconds."
"We would like to see some improvement in the performance of large scale procedures, such as when we migrate from Oracle to csSQL."
"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."
"Whatever solution worked today can not be reused in the next migration."
"There are a set of complexities and challenges when a user wants to integrate AWS products with Microsoft products."
"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."
"I think that Amazon needs to improve the migration scenarios after analytics"
"More endpoints need to be supported by AWS Database Migration Service. There's also a need for more control and transparency on the product, including better technical support."
"The product's setup process could be simpler."
"There are no concurrent licenses, they only have seat licenses on cloud. That's the whole challenge. For example, if in any project your headcount increases or decreases, you do not have that concurrence and you have a seat license, you run into challenges because you have to procure a few more licenses for getting the job done."
"Due to using the open-source version of Talend Data Integration, which lacks a scheduler, our current approach involves developing jobs in Talend, exporting them as Java packages, and utilizing an external scheduler, such as Windows Scheduler, to manage the scheduling process."
"Sometimes there are bugs which are unidentified and we have to follow-up with the Talend team to resolve them. In a critical situation, it takes time for them to update patches."
"The tool's technical support needs to be better. It doesn't have a local data center but pushes everything to the cloud. They need to check in with customers to see if they're happy and how well the solutions work. They need to assign a customer success manager for the accounts they sell."
More AWS Database Migration Service Pricing and Cost Advice →
AWS Database Migration Service is ranked 2nd in Cloud Data Integration with 27 reviews while Talend Data integration is ranked 23rd in Cloud Data Integration with 5 reviews. AWS Database Migration Service is rated 7.8, while Talend Data integration is rated 8.6. 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 Talend Data integration writes "Very affordable and on par with much more expensive solutions". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Qlik Replicate, Fivetran and Confluent, whereas Talend Data integration is most compared with Talend Open Studio, SAP Cloud Platform, Oracle Data Integrator (ODI), AWS Glue and Microsoft Azure Logic Apps. See our AWS Database Migration Service vs. Talend Data integration 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.