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

AWS Database Migration Service vs Pentaho Data Integration and Analytics 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.8
Number of Reviews
30
Ranking in other categories
Cloud Data Integration (2nd)
Pentaho Data Integration an...
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
53
Ranking in other categories
Data Integration (23rd)
 

Featured Reviews

Avinash Gangu - PeerSpot reviewer
Centralizing database tables enhances workflow efficiency for ease of use
I was looking for some content as part of a comparison analysis. However, one of the pain points is that it is way too free-flowing. I have to skim through all the security pages to get to the crux of it. I was looking for a table that suggests which facets such services address with proofs of reference from professional conferences. The document is a 63-page read, making it very difficult to navigate without a summary. I was looking for a summary at the start, however, if I have to do it myself, I might as well integrate from AWS Docs and then Informative Exchange. The current document contains a lot of information, which is great, but there needs to be a summary indicating the story's essence. Unless there's a correction, it is not present in the document.
Ryan Ferdon - PeerSpot reviewer
Low-code makes development faster than with Python, but there were caching issues
If you're working with a larger data set, I'm not so sure it would be the best solution. The larger things got the slower it was. It was kind of buggy sometimes. And when we ran the flow, it didn't go from a perceived start to end, node by node. Everything kicked off at once. That meant there were times when it would get ahead of itself and a job would fail. That was not because the job was wrong, but because Pentaho decided to go at everything at once, and something would process before it was supposed to. There were nodes you could add to make sure that, before this node kicks off, all these others have processed, but it was a bit tedious. There were also caching issues, and we had to write code to clear the cache every time we opened the program, because the cache would fill up and it wouldn't run. I don't know how hard that would be for them to fix, or if it was fixed in version 10. Also, the UI is a bit outdated, but I'm more of a fan of function over how something looks. One other thing that would have helped with Pentaho was documentation and support on the internet: how to do things, how to set up. I think there are some sites on how to install it, and Pentaho does have a help repository, but it wasn't always the most useful.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's scalable."
"We particularly like that this solution has the facility to integrate with all ETL tools."
"The product's initial setup phase was very easy."
"This efficient workflow has been particularly helpful."
"The most valuable feature is its ability to get all the changes in our data and store that in an S3 bucket."
"The solution is stable and reliable."
"I like that I can focus on the logic and I don't have to worry about the administration stuff. AWS handles that for me."
"The product is cheaper than all platforms"
"I can create faster instructions than writing with SQL or code. Also, I am able to do some background control of the data process with this tool. Therefore, I use it as an ELT tool. I have a station area where I can work with all the information that I have in my production databases, then I can work with the data that I created."
"We also haven't had to create any custom Java code. Almost everywhere it's SQL, so it's done in the pipeline and the configuration. That means you can offload the work to people who, while they are not less experienced, are less technical when it comes to logic."
"Pentaho Data Integration is quite simple to learn, and there is a lot of information available online."
"Flexible deployment, in any environment, is very important to us. That is the key reason why we ended up with these tools. Because we have a very highly secure environment, we must be able to install it in multiple environments on multiple different servers. The fact that we could use the same tool in all our environments, on-prem and in the cloud, was very important to us."
"The solution has a free to use community version."
"We use Lumada’s ability to develop and deploy data pipeline templates once and reuse them. This is very important. When the entire pipeline is automated, we do not have any issues in respect to deployment of code or with code working in one environment but not working in another environment. We have saved a lot of time and effort from that perspective because it is easy to build ETL pipelines."
"This solution allows us to create pipelines using a minimal amount of custom coding."
"We can schedule job execution in the BA Server, which is the front-end product we're using right now. That scheduling interface is nice."
 

Cons

"The live duplication has a delay of two minutes, which can be an issue."
"The solution’s scalability and performance could be improved."
"In my experience, AWS Database Migration Service performs well for its primary purpose of data migration. One area that could be improved is its support for non-AWS file formats, particularly when integrating data from sources stored outside of AWS. For example, handling AWS Data Lakes, Delta Lake, or Hadoop file formats stored in S3 requires extensive configuration and isn't always straightforward. It would be beneficial to streamline this process to ensure smoother migrations from non-AWS environments to AWS. As for additional functionality, I think enhancing support for these external file formats and simplifying configuration steps would be valuable improvements for the service."
"This solution is compatible with only AWS."
"AWS Database Migration Service can become complex when testing. Other solutions, such as Microsoft Azure makes it easy to do. There are more steps to complete tasks in AWS Database Migration Service than in Microsoft Azure."
"There is no connectivity to the source database or the target database."
"This solution can offer more tweaks where the latency can be brought down to fifteen seconds."
"Database Migration Service could be more integrated. I think that it makes sense to add integration to these functions. For example, AWS Glue has a feature called Orchestrator to create data flows, and that's more straightforward."
"I'm still in the very recent stage concerning Pentaho Data Integration, but it can't really handle what I describe as "extreme data processing" i.e. when there is a huge amount of data to process. That is one area where Pentaho is still lacking."
"The web interface is rusty, and the biggest problem with Pentaho is debugging and troubleshooting. It isn't easy to build the pipeline incrementally. At least in our case, it's hard to find a way to execute step by step in the debugging mode."
"I work with different databases. I would like to work with more connectors to new databases, e.g., DynamoDB and MariaDB, and new cloud solutions, e.g., AWS, Azure, and GCP. If they had these connectors, that would be great. They could improve by building new connectors. If you have native connections to different databases, then you can make instructions more efficient and in a more natural way. You don't have to write any scripts to use that connector."
"A big problem after deploying something that we do in Lumada is with Git. You get a binary file to do a code review. So, if you need to do a review, you have to take pictures of the screen to show each step. That is the biggest bug if you are using Git."
"​I could not connect to our Hadoop environment in an easy and flexible way, and it was important to scale our data warehouse​."
"The product needs more plugins."
"If you develop it on MacBook, it'll be quite a hassle."
"In the Community edition, it would be nice to have more modules that allow you to code directly within the application. It could have R or Python completely integrated into it, but this could also be because I'm using an older version."
 

Pricing and Cost Advice

"I rate the product price a seven on a scale of one to ten, where one is a high price, and ten is a low price."
"For Egypt, the product's prices are high, making it a specific problem in one region and not globally."
"I would rate the pricing a seven out of ten."
"In terms of pricing, I'd rate it an eight out of ten, considering it's a well-priced solution."
"AWS Database Migration Service is very inexpensive."
"The pricing is on the higher side."
"Cost is the only factor that is challenging."
"Pricing can be improved."
"There is a good open source option (Community Edition)​."
"There was a cost analysis done and Pentaho did favorably in terms of cost."
"I believe the pricing of the solution is more affordable than the competitors"
"You need to go through the paid version to have Hitachi Lumada specialized support. However, if you are using the free version, then you will have only the community support. You will depend on the releases from Hitachi to solve some problem or questions that you have, such as bug fixes. You will need to wait for the newest versions or releases to solve these types of problems."
"If a company is looking for an ETL solution and wants to integrate it with their tech stack but doesn't want to spend a bunch of money, Pentaho is a good solution"
"The price of the regular version is not reasonable and it should be lower."
"I think Lumada's price is fair compared to some of the others, like BusinessObjects, which is was the other thing that I used at my previous job. BusinessObject's price was more reasonable before SAP acquired it. They jacked the price up significantly. Oracle's OBIEE tool was also prohibitively expensive."
"Sometimes we provide the licenses or the customer can procure their own licenses. Previously, we had an enterprise license. Currently, we are on a community license as this is adequate for our needs."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
15%
Manufacturing Company
7%
Government
7%
Financial Services Firm
21%
Computer Software Company
15%
Government
8%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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...
Which ETL tool would you recommend to populate data from OLTP to OLAP?
Hi Rajneesh, yes here is the feature comparison between the community and enterprise edition : https://www.hitachivantara.com/en-us/pdf/brochure/leverage-open-source-benefits-with-assurance-of-hita...
What do you think can be improved with Hitachi Lumada Data Integrations?
In my opinion, the reporting side of this tool needs serious improvements. In my previous company, we worked with Hitachi Lumada Data Integration and while it does a good job for what it’s worth, ...
What do you use Hitachi Lumada Data Integrations for most frequently?
My company has used this product to transform data from databases, CSV files, and flat files. It really does a good job. We were most satisfied with the results in terms of how many people could us...
 

Also Known As

AWS Data Migration Service
Hitachi Lumada Data Integration, Kettle, Pentaho Data Integration
 

Overview

 

Sample Customers

Veoci, Trimble, Nasdaq, shaadi.com, Hotelbeds, SysAid, Verizon, Expedia, Pega
66Controls, Providential Revenue Agency of Ro Negro, NOAA Information Systems, Swiss Real Estate Institute
Find out what your peers are saying about AWS Database Migration Service vs. Pentaho Data Integration and Analytics and other solutions. Updated: January 2025.
838,713 professionals have used our research since 2012.