How extract-transform-load and extract-load-transform differ, and why ELT is common in modern lakehouses.
From Ultra Transcenders DP-900 by Tony Rough (publishing soon)
Getting data out of operational systems and into an analytical store is the job of a data pipeline. The two patterns differ in one respect: where the transformation happens.
Extract, transform, load (ETL) extracts data from the sources, transforms it according to business rules in a separate, specialised engine (often using staging tables to hold data while it is processed), and then loads the result into the destination. Transformations typically include filtering, sorting, aggregating, joining, cleaning, deduplicating and validating data.
Extract, load, transform (ELT) extracts the data and loads it into the target store first, then transforms it there, using the target store’s own processing power. Learn notes that ELT is common in modern lakehouses. Its advantages are a simpler architecture (no separate transformation engine) and performance that scales with the target store. It only works well, though, when the target system is powerful enough to transform the data efficiently. Figure 2.2 compares where the transformation runs in each pattern.
| Aspect | ETL | ELT |
|---|---|---|
| Order of steps | Extract, transform, then load | Extract, load, then transform |
| Where transformation runs | A separate transformation engine before the target | Inside the target data store |
| Raw data in the target | No, only transformed data arrives | Yes, raw data is loaded and kept |
| Typical fit | Constrained target systems, complex business rules, curated staging audits before loading | Modern warehouses and lakehouses with elastic compute; keeping raw data for exploration or future schema changes |
On Azure, pipelines are built with Data Factory in Microsoft Fabric for work inside Fabric, or with the standalone Azure Data Factory service. Both are described in Chapter 7, Large-scale analytics: Microsoft Fabric and Azure Databricks.
Common trap: Thinking ELT skips transformation - ELT still transforms the data; the difference from ETL is only where and when, with the transformation running inside the target store after loading.
This note is one section of Ultra Transcenders DP-900: Microsoft Azure Data Fundamentals, an independent study guide that explains every topic the exam covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to Microsoft Learn.
Publishing soon on Amazon in Kindle and paperback editions.
About the book · DP-900 terms in the glossary · All DP-900 study notes
What each ACID property guarantees in a transactional (OLTP) database, with the classic funds-transfer example.
How OLTP and analytical systems differ in purpose, data shape, queries and users.
How normalisation splits data into one table per entity, linked by keys, so each fact is stored once.
The three Azure SQL options side by side: IaaS or PaaS, compatibility, management and availability.
Which Azure SQL option or open-source database service fits a requirement, and why.
Storage and access costs, minimum retention periods, Archive rehydration and lifecycle management policies.
The key characteristics of Azure Cosmos DB: schema-agnostic items, automatic indexing, global distribution and low latency.