We performed a comparison between AWS Glue and Palantir Foundry 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."Glue is a NoSQL-based data ETL tool that has some advantages over IIS and ISAs."
"One of the best features of the solution is its ability to easily integrate with other AWS services."
"AWS Glue's most valuable features are the data catalog, including crawlers and tables, and Glue Studio, which means you don't have to use custom code."
"The product has a valuable feature for data catalog."
"It's fairly straightforward as a product; it's not very complicated."
"I like that it's flexible, powerful, and allows you to write your own queries and scripts to get the needed transformations."
"The solution helps organizations gain flexibility in defining the structure of the data."
"What I like best about AWS Glue is its real-time data backup feature. Last week, there was a production push, and what used to take almost ten days to send out around fifty-six thousand emails now takes only two hours."
"The solution provides an end-to-end integrated tech stack that takes care of all utility/infrastructure topics for you."
"The virtualization tool is useful."
"The data lineage is great."
"The ease of use is my favorite feature. We're able to build different models and projects or combine different projects to build one use case."
"The security is also excellent. It's highly granular, so the admins have a high degree of control, and there are many levels of security. That worked well. You won't have an EDC unless you put everything onto the platform because it is its own isolated thing."
"The solution offers very good end-to-end capabilities."
"The interface is really user-friendly."
"It is easy to map out a workflow and run trigger-based scripts without having to deploy to another server."
"It would be better if it were more user-friendly. The interesting thing we found is that it was a little strange at the beginning. The way Glue works is not very straightforward. After trying different things, for example, we used just the console to create jobs. Then we realized that things were not working as expected. After researching and learning more, we realized that even though the console creates the script for the ETL processes, you need to modify or write your own script in Spark to do everything you want it to do. For example, we are pulling data from our source database and our application database, which is in Aurora. From there, we are doing the ETL to transform the data and write the results into Redshift. But what was surprising is that it's almost like whatever you want to do, you can do it with Glue because you have the option to put together your own script. Even though there are many functionalities and many connections, you have the opportunity to write your own queries to do whatever transformations you need to do. It's a little deceiving that some options are supposed to work in a certain way when you set them up in the console, but then they are not exactly working the right way or not as expected. It would be better if they provided more examples and more documentation on options."
"The crucial problem with AWS Glue is that it only works with AWS. It is not an agnostic tool like Pentaho. In PowerCenter, we can install the forms from Google and other vendors, but in the case of AWS Glue, we can only use AWS."
"I haven't looked into Glue in terms of seeking out flaws. I've not come across missing features."
"I would like to see stable libraries at the moment they are not there."
"Overall, I consider the technical support to be fine, although the response time could be faster in certain cases."
"The product is expensive for data streaming. This area needs improvement."
"Cost-wise, AWS Glue is expensive, so that's an area for improvement. The process for setting up the solution was also complex, which is another area for improvement."
"There should be more connectors for different databases."
"The frontend capabilities of Palantir Foundry could be improved."
"Compared to other hyperscalers, Palantir Foundry is complex and not so user-intuitive."
"There is not a wide user base for the solution's online documentation so it is sometimes difficult to find answers."
"The solution could use more online documentation for new users."
"It requires a lot of manual work and is very time-consuming to get to a functional point."
"It would be helpful to build applications based on Azure functions or web apps in Palantir Foundry."
"Cost of this solution is quite high."
"Difficult to receive data from external sources."
AWS Glue is ranked 1st in Cloud Data Integration with 37 reviews while Palantir Foundry is ranked 12th in Cloud Data Integration with 14 reviews. AWS Glue is rated 7.8, while Palantir Foundry is rated 7.6. The top reviewer of AWS Glue writes "Provides serverless mechanism, easy data transformation and automated infrastructure management". On the other hand, the top reviewer of Palantir Foundry writes "The data visualization is fantastic and the security is excellent". AWS Glue is most compared with AWS Database Migration Service, Informatica PowerCenter, SSIS, Informatica Cloud Data Integration and Denodo, whereas Palantir Foundry is most compared with Azure Data Factory, Palantir Gotham, SAP Data Services, Alteryx Designer and Denodo. See our AWS Glue vs. Palantir Foundry 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.