liveBook · Manning

Etlt

As explained in Snowflake Data Engineering

ETLT is a data pipeline pattern that performs simple transformations before loading and complex business transformations after loading.

ETLT (extract-transform-load-transform) combines ETL and ELT: it performs simple transformations before loading data, then applies complex business transformations after loading, where Snowflake compute resources can process them. section 11.3

A typical ETLT flow separates responsibilities across pipeline stages:

  • Extract data from operational databases or files. section 11.0
  • Apply simple transformations before loading the data. section 11.3
  • Load the prepared data into Snowflake. section 11.3
  • Perform complex business transformations inside Snowflake using its compute resources. section 11.3

Organize intermediate outputs into layers such as extraction, staging, data warehouse, and presentation. These layers are optional, but separating flows by layer helps keep pipeline dependencies orderly; outputs may be tables, materialized views, dynamic tables, or views. section 11.3

How Snowflake Data Engineering covers it

How deep it goes
Defines the two transformation stages and layer organization but does not provide implementation code or detailed transformation steps.
Examples
Uses a fictional bakery pipeline sourcing relational tables, files, and other business data.
What it assumes
Assumes familiarity with extracting, loading, transforming, and storing data while establishing pipeline design fundamentals.
What you can do after
Evaluate ETL, ELT, and ETLT choices and organize transformations across pipeline layers.
How it connects
Connects ETL, ELT, data transformation layers, Snowflake compute, and intermediate database objects.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Snowflake Data Engineering. The section links point to the parts of the book it draws on.