StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Big Data Tools
  5. AWS Glue vs Trifacta

AWS Glue vs Trifacta

OverviewDecisionsComparisonAlternatives

Overview

Trifacta
Trifacta
Stacks19
Followers41
Votes0
AWS Glue
AWS Glue
Stacks461
Followers819
Votes9

AWS Glue vs Trifacta: What are the differences?

AWS Glue vs Trifacta

AWS Glue and Trifacta are two popular tools used for data preparation and transformation. While both tools serve similar purposes, there are key differences between them.

  1. Data Source Compatibility: AWS Glue supports a wide range of data sources including Amazon S3, Amazon RDS, and Amazon Redshift. Trifacta, on the other hand, supports a broader range of data sources including files, databases, and cloud storage from different vendors.

  2. Data Transformation Capabilities: AWS Glue provides various data transformation capabilities like filtering, mapping, and aggregation. Trifacta offers a more advanced set of transformations such as parsing complex structures, manipulating JSON data, and handling unstructured data with machine learning algorithms.

  3. Data Quality and Validation: AWS Glue focuses on data quality and validation by providing built-in data quality checks. Trifacta, on the other hand, offers more extensive data profiling and validation features including the ability to define custom rules for data quality.

  4. Collaboration and Workflow management: Trifacta provides better collaboration and workflow management capabilities with features like shared projects, version control, and role-based access control. AWS Glue, on the other hand, offers limited collaboration features and is more suited for individual users.

  5. Performance and Scalability: AWS Glue is fully managed and automatically scales based on the workload, ensuring high performance and scalability. Trifacta, although scalable, requires manual configuration and optimization to achieve similar performance in large-scale data processing scenarios.

  6. Cost: AWS Glue pricing is based on the number of data processing units (DPUs) and the amount of data processed, making it more cost-efficient for smaller workloads. Trifacta, on the other hand, has a subscription-based pricing model, which can be more cost-effective for larger workloads or organizations with predictable data processing needs.

In summary, AWS Glue offers broad data source support, while Trifacta provides advanced data transformation capabilities and extensive collaboration features. AWS Glue's focus is on data quality and validation, while Trifacta offers better performance optimization and scalability options. The choice between the two tools ultimately depends on the specific requirements and priorities of the organization or individual users.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Trifacta, AWS Glue

Vamshi
Vamshi

Data Engineer at Tata Consultancy Services

May 29, 2020

Needs adviceonPySparkPySparkAzure Data FactoryAzure Data FactoryDatabricksDatabricks

I have to collect different data from multiple sources and store them in a single cloud location. Then perform cleaning and transforming using PySpark, and push the end results to other applications like reporting tools, etc. What would be the best solution? I can only think of Azure Data Factory + Databricks. Are there any alternatives to #AWS services + Databricks?

269k views269k
Comments
Sarah
Sarah

Jun 25, 2020

Needs adviceonOpenRefineOpenRefine

I'm looking for an open-source/free/cheap tool to clean messy data coming from various travel APIs. We use many different APIs and save the info in our DB. However, many duplicates cannot be easily recognized as such.

We would either write an algorithm or use smart technology/tools with ML to help with product management.

While there are many things to be considered, this is one feature that it should have:

"To avoid confusion, we need to merge the suppliers & products accordingly. Products and suppliers must be able to be merged and assigned separately.

Reason: It may happen that one supplier offers different products. E.g., 1 tour operator offers 3 products via 1 API, but only 1 product with 3 (or a different amount of) variations via a different API. Also, the commission may differ for products, which we need to consider. Very often, products that are live (are bookable in real-time) on via 1 API, but are not live on the other. E.g., Supplier product 1 & 2 of API1 are live, product 3 not. For the same supplier, API2 provides live availability for products 1, 2, and 3.

Summing up, when merging the suppliers (tour operators) we need to consider:

  • Are the products the same for all APIs?
  • Which booking system API gives a better commission? Note: Some APIs charge us 1-5% depending on the monthly sale, which needs to be considered
  • Which booking system provides live availability
  • Is it the same supplier, or is the name only similar?

Most of the time, the supplier names differ even if they are the same (e.g., API1 often names them XX Pty Ltd, while API2 leaves "Pty Ltd" out). Additionally, the product title, description, etc. differ.

We need to write logic and create an algorithm to find the duplicates & to merge, assign, or (de)activate the respective supplier or product. My previous developer started a module to merge the suppliers, which does not seem to work correctly. Also, it is way too time taking considering the high amount of products that we have.

I would recommend merging, assigning etc. products and suppliers only if our algorithm says it's 90- 100% the matching supplier/product. Otherwise, admins need to be able to check & modify this. E.g. everything with a lower possibility of matching will be matched automatically, but can be undone or modified.

The next time the cron job runs, this needs to be considered to avoid recreating duplicates & creating a mess."

I am not sure in what way OpenRefine can help to achieve this and what ML tool can be connected to learn from the decisions the product management team makes. Maybe you have an idea of how other travel portals deal with messy data, duplicates, etc.?

I'm looking for the cheapest solution for a start-up, but it should do the work properly.

19.2k views19.2k
Comments
datocrats-org
datocrats-org

Jul 29, 2020

Needs adviceonAmazon EC2Amazon EC2TableauTableauPowerBIPowerBI

We need to perform ETL from several databases into a data warehouse or data lake. We want to

  • keep raw and transformed data available to users to draft their own queries efficiently
  • give users the ability to give custom permissions and SSO
  • move between open-source on-premises development and cloud-based production environments

We want to use inexpensive Amazon EC2 instances only on medium-sized data set 16GB to 32GB feeding into Tableau Server or PowerBI for reporting and data analysis purposes.

319k views319k
Comments

Detailed Comparison

Trifacta
Trifacta
AWS Glue
AWS Glue

It is an Intelligent Platform that Interoperates with Your Data Investments. It sits between the data storage and processing environments and the visualization, statistical or machine learning tools used downstream

A fully managed extract, transform, and load (ETL) service that makes it easy for customers to prepare and load their data for analytics.

Interactive Exploration; Automated visual representations of data based upon its content in the most compelling visual profile; Predictive Transformation; Intelligent Execution; Collaborative Data Governance.
Easy - AWS Glue automates much of the effort in building, maintaining, and running ETL jobs. AWS Glue crawls your data sources, identifies data formats, and suggests schemas and transformations. AWS Glue automatically generates the code to execute your data transformations and loading processes.; Integrated - AWS Glue is integrated across a wide range of AWS services.; Serverless - AWS Glue is serverless. There is no infrastructure to provision or manage. AWS Glue handles provisioning, configuration, and scaling of the resources required to run your ETL jobs on a fully managed, scale-out Apache Spark environment. You pay only for the resources used while your jobs are running.; Developer Friendly - AWS Glue generates ETL code that is customizable, reusable, and portable, using familiar technology - Scala, Python, and Apache Spark. You can also import custom readers, writers and transformations into your Glue ETL code. Since the code AWS Glue generates is based on open frameworks, there is no lock-in. You can use it anywhere.
Statistics
Stacks
19
Stacks
461
Followers
41
Followers
819
Votes
0
Votes
9
Pros & Cons
No community feedback yet
Pros
  • 9
    Managed Hive Metastore
Integrations
Microsoft Azure
Microsoft Azure
Google Cloud Storage
Google Cloud Storage
Snowflake
Snowflake
AWS Data Pipeline
AWS Data Pipeline
Tableau
Tableau
Amazon Redshift
Amazon Redshift
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
Amazon Athena
Amazon Athena
MySQL
MySQL
Microsoft SQL Server
Microsoft SQL Server
Amazon EMR
Amazon EMR
Amazon Aurora
Amazon Aurora
Oracle
Oracle
Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL

What are some alternatives to Trifacta, AWS Glue?

Apache Spark

Apache Spark

Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.

Presto

Presto

Distributed SQL Query Engine for Big Data

Amazon Athena

Amazon Athena

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.

Apache Flink

Apache Flink

Apache Flink is an open source system for fast and versatile data analytics in clusters. Flink supports batch and streaming analytics, in one system. Analytical programs can be written in concise and elegant APIs in Java and Scala.

lakeFS

lakeFS

It is an open-source data version control system for data lakes. It provides a “Git for data” platform enabling you to implement best practices from software engineering on your data lake, including branching and merging, CI/CD, and production-like dev/test environments.

Druid

Druid

Druid is a distributed, column-oriented, real-time analytics data store that is commonly used to power exploratory dashboards in multi-tenant environments. Druid excels as a data warehousing solution for fast aggregate queries on petabyte sized data sets. Druid supports a variety of flexible filters, exact calculations, approximate algorithms, and other useful calculations.

Apache Kylin

Apache Kylin

Apache Kylin™ is an open source Distributed Analytics Engine designed to provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop/Spark supporting extremely large datasets, originally contributed from eBay Inc.

Splunk

Splunk

It provides the leading platform for Operational Intelligence. Customers use it to search, monitor, analyze and visualize machine data.

Apache Impala

Apache Impala

Impala is a modern, open source, MPP SQL query engine for Apache Hadoop. Impala is shipped by Cloudera, MapR, and Amazon. With Impala, you can query data, whether stored in HDFS or Apache HBase – including SELECT, JOIN, and aggregate functions – in real time.

Vertica

Vertica

It provides a best-in-class, unified analytics platform that will forever be independent from underlying infrastructure.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase