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

AWS AppSync 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 AppSync
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
2
Ranking in other categories
Cloud Data Integration (23rd)
Pentaho Data Integration an...
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
53
Ranking in other categories
Data Integration (22nd)
 

Featured Reviews

Akil Saji - PeerSpot reviewer
Ease of creating APIs with ongoing updates needed for automation
AWS has made it easy for developers like me to create and manage GraphQL APIs. The ease of use is a main advantage, allowing even beginners to start from scratch and learn through AppSync. Before AWS, developing and managing APIs was quite complex. AWS provided AppSync, which assists developers and startup founders. Startups blooming everywhere benefit from this service, welcoming those who lack prior knowledge. When working on AWS, I notice that Amazon regularly implements new features. For instance, with the Lambda service, AWS is transitioning from an old editor to a new one. Similarly, AppSync frequently introduces updates and changes. This trend is making the user interface more accessible, even for individuals without a technical background. Additionally, the cost is attractive, as AWS operates on a pay-as-you-go basis. These factors make AppSync both easy to use and cost-effective.
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

"Support for multiple data sources and formats is a fantastic feature."
"AWS has made it easy for developers like me to create and manage GraphQL APIs."
"AWS has made it easy for developers like me to create and manage GraphQL APIs."
"It has a really friendly user interface, which is its main feature. The process of automating or combining SQL code with some databases and doing the automation is great and really convenient."
"Pentaho Data Integration is easy to use, especially when transforming data."
"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."
"I can use Python, which is open-source, and I can run other scripts, including Linux scripts. It's user-friendly for running any object-based language. That's a very important feature because we live in a world of open-source."
"I find the drag and drop feature in Pentaho Data Integration very useful for integration."
"The fact that it's a low-code solution is valuable. It's good for more junior people who may not be as experienced with programming."
"We're using the PDI and the repository function, and they give us the ability to easily generate reporting and output, and to access data. We also like the ability to schedule."
"The way it has improved our product is by giving our users the ability to do ad hoc reports, which is very important to our users. We can do predictive analysis on trends coming in for contracts, which is what our product does. The product helps users decide which way to go based on the predictive analysis done by Pentaho. Pentaho is not doing predictions, but reporting on the predictions that our product is doing. This is a big part of our product."
 

Cons

"Moving to other clouds is impossible without significantly rearchitecting your applications."
"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."
"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."
"Its basic functionality doesn't need a whole lot of change. There could be some improvement in the consistency of the behavior of different transformation steps. The software did start as open-source and a lot of the fundamental, everyday transformation steps that you use when building ETL jobs were developed by different people. It is not a seamless paradigm. A table input step has a different way of thinking than a data merge step."
"Parallel execution could be better in Pentaho. It's very simple but I don't think it works well."
"Although it is a low-code solution with a graphical interface, often the error messages that you get are of the type that a developer would be happy with. You get a big stack of red text and Java errors displayed on the screen, and less technical people can get intimidated by that. It can be a bit intimidating to get a wall of red error messages displayed. Other graphical tools that are focused at the power user level provide a much more user-friendly experience in dealing with your exceptions and guiding the user into where they've made the mistake."
"Should provide additional control for the data warehouse"
"The performance could be improved. If they could have analytics perform well on large volumes, that would be a big deal for our products."
"One thing that I don't like, just a little, is the backward compatibility."
"It could be better integrated with programming languages, like Python and R. Right now, if I want to run a Python code on one of my ETLs, it is a bit difficult to do. It would be great if we have some modules where we could code directly in a Python language. We don't really have a way to run Python code natively."
"Some of the scheduling features about Lumada drive me buggy. The one issue that always drives me up the wall is when Daylight Savings Time changes. It doesn't take that into account elegantly. Every time it changes, I have to do something. It's not a big deal, but it's annoying."
 

Pricing and Cost Advice

"Licensing fees are paid on a monthly basis, and it is a pay-as-you-go model."
"There is a good open source option (Community Edition)​."
"We did a two or three-year deal the last time we did it. As compared to other solutions, at least so far in our experience, it has been very affordable. The licensing is by component. So, you need to make sure you only license the components that you really intend to use. I am not sure if we have relicensed after the Hitachi acquisition, but previously, multi-year renewals resulted in a good discount. I'm not sure if this is still the case. We've had the full suite for a lot of years, and there is just the initial cost. I am not aware of any additional costs."
"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."
"The solution reduced our ETL development time by a lot because a whole project used to take about a month to get done previously. After having Lumada, it took just a week. For a big company in Brazil, it saves a team at least $10,000 a month."
"I use it because it is free. I download from their page for free. I don't have to pay for a license. With other tools, I have to pay for the licenses. That is why I use Pentaho."
"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."
"The cost of these types of solutions are expensive. So, we really appreciate what we get for our money. Though, we don't think of the solution as a top-of-the-line solution or anything like that."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Computer Software Company
17%
Healthcare Company
9%
Comms Service Provider
7%
Financial Services Firm
22%
Computer Software Company
15%
Government
8%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for AWS AppSync?
We initially had limited knowledge about AWS costs. As beginners, we ran many instances for over a month. Consequently, we received a bill from Amazon for around $20, which was unexpected. This hig...
What needs improvement with AWS AppSync?
In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial. Regular updates might soon address th...
What is your primary use case for AWS AppSync?
Our company handles in-house projects and serves clients globally. My role with AppSync involves creating GraphQL APIs. There are different types of APIs, such as REST API, GraphQL API, and WebSock...
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

AppSync
Hitachi Lumada Data Integration, Kettle, Pentaho Data Integration
 

Overview

 

Sample Customers

ACBL, Puresec, IDT, ASU, Public Good, cookpad, ALDO, ticketmaster
66Controls, Providential Revenue Agency of Ro Negro, NOAA Information Systems, Swiss Real Estate Institute
Find out what your peers are saying about AWS AppSync vs. Pentaho Data Integration and Analytics and other solutions. Updated: April 2025.
849,686 professionals have used our research since 2012.