Extract, load, transform

From HandWiki

Extract, load, transform (ELT) is an alternative to extract, transform, load (ETL) used with data lake implementations. In contrast to ETL, in ELT models the data is not transformed on entry to the data lake, but stored in its original raw format. This enables faster loading times. However, ELT requires sufficient processing power within the data processing engine to carry out the transformation on demand, to return the results in a timely manner.[1][2] Since the data is not processed on entry to the data lake, the query and schema do not need to be defined a priori (although often the schema will be available during load since many data sources are extracts from databases or similar structured data systems and hence have an associated schema). ELT is a data pipeline model.[3][4]

Benefits

Some of the benefits of an ELT process include speed and the ability to handle both structured and unstructured data.[5]

Cloud data lake components

Common storage options

Querying

  • AWS
    • Redshift Spectrum
    • Athena
    • EMR (Presto)
  • Azure
  • GCP
    • BigQuery

References

  1. ↑ "What is ELT (Extract, Load, Transform)? | IBM" (in en-us). https://www.ibm.com/topics/elt. 
  2. ↑ Abdullahi, Aminu (2023-06-30). "ETL vs ELT: What Are the Main Differences and Which Is Better?" (in en-US). https://www.techrepublic.com/article/etl-vs-elt/. 
  3. ↑ Using Redshift Spectrum to load data pipelines Published by deductive.com on January 17, 2018, retrieved on April 3, 2019.
  4. ↑ "What is ELT (Extract, Load, Transform)? | dbt Developer Hub" (in en). 2024-01-30. https://docs.getdbt.com/terms/elt. 
  5. ↑ Mishra, Tanya (2023-09-02). "ETL vs ELT: Meaning, Major Differences & Examples" (in en-US). https://www.analyticsinsight.net/etl-vs-elt-meaning-major-differences-examples/. 

External links




Retrieved from "https://handwiki.org/wiki/index.php?title=Extract,_load,_transform&oldid=3375707"