We performed a comparison between AWS Database Migration Service, Jitterbit Harmony , and Quest SharePlex based on real PeerSpot user reviews.
Find out what your peers are saying about Amazon Web Services (AWS), MuleSoft, Matillion and others in Cloud Data Integration."AWS Database Migration Service is good for smaller workloads and provides compatibility."
"I am very impressed by the scalability of AWS Database Migration Service."
"The solution is instantaneous. We can launch the service and reduce the end number of manpower."
"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."
"The solution is stable and reliable."
"Scalable and stable solution for migrating databases to AWS, with valuable features such as parallel full load and continuous data replication."
"We particularly like that this solution has the facility to integrate with all ETL tools."
"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."
"Integrity, ease of use, user-friendly user interface, and errorless logs are the most valuable features."
"It is very easy to build integrations and processes to pull and push data."
"The fluid user interface (probably the most user friendly interface, when compared to its competitors)."
"The Cloud Console for monitoring and troubleshooting data operations."
"It runs like an appliance and has tremendous throughput."
"Jitterbit handles the most lines of data in a .csv and loads the quickest of any data loader I have tried."
"Jitterbit provides the ability to quickly map data between files and databases."
"Easy integration with Salesforce"
"Because of the volume of the transactions, we heavily use a feature that allows SharePlex to replicate thousands of transactions. It's called PEP, Post Enhancement Performance, and that has helped us scale tremendously."
"The core replication and its performance. Performance is crucial, and SharePlex is by far the fastest. The way it handles replication to multiple targets along with basic filtering, as well as from multiple sources to a single target, is very efficient."
"The core features of the solution we like are the reliability of the data transfer and the accuracy of data read and write. The stability of the solution is also excellent."
"I like SharePlex's Compare and Repair tool."
"There are some capabilities within SharePlex where you can see how the data is migrating and if it still maintains good data integrity. For example, if there are some tables that get out of sync, there are ways to find them and fix the problem on the spot. Since these are very common issues, we can easily fix these types of problems using utilities, like compare and repair. So, if you find something is out of sync, then you can just repair that table. It basically syncs that table from source to target to see if there are any differences. It will then replicate those differences to the target."
"The solution’s scalability and performance could be improved."
"Whatever solution worked today can not be reused in the next migration."
"The way that the task settings work, specifically for logging, is really poor."
"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."
"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."
"This solution is compatible with only AWS."
"The initial setup can be difficult for beginners in AWS Database Migration Service. You will need the training to complete it."
"It would be helpful if the bandwidth could be independent of the network or if we could have a dedicated bandwidth for this product."
"You need to have some development skills or hire a Jitterbit engineer to make changes."
"I would like the ability to offer a dedicated cloud version for security."
"The initial setup can be a little bit difficult."
"There were some bugs in the product. For example if you run a delete query and test, it deletes the actual data."
"Its API management capabilities need improvement."
"I know with Salesforce updating the UI like they did, it slowed it down a lot."
"Looping through complex data structures can be difficult."
"In the past few months, there have been some server downtimes during work hours that have affected some critical scheduled integrations."
"For its function in relation to replication (i.e. filtering), I'd give it a six or seven out of 10. GoldenGate has much more functionality by comparison."
"I would like more ability to automate installation and configuration in line with some of the DevOps processes that are more mature in the market. That would be a considerable improvement."
"I would like the solution to have some kind of machine learning and AI capabilities. Often, if we want to improve the performance of posting, we have to bump up a parameter. That means we need to stop the process, come up with a figure that we want to bump the parameter up to, and then start SharePlex. Machine learning and AI capabilities for these kinds of improvement would tremendously help boost productivity for us."
"The reporting features need improvement. It would be very good for users to have a clear understanding of the status of replication."
"I don't know how easy it would be to change the architecture in an already implemented replication. For example, if we have a certain way of architecting for a particular database migration and want to change that during a period of time, is that an easy or difficult change? There was a need for us to change the architecture in-between the migration, but we didn't do it. We thought, "This is possibly complicated. Let's not change it in the middle because we were approaching our cutover date." That was one thing that we should have checked with support about for training."
More AWS Database Migration Service Pricing and Cost Advice →
