The Incremental ETL Architecture
summary
Incremental ETL at big scale uses Apache Spark Structured Streaming with Delta Lake tables and Databricks Autoloader to move only new or changed rows, keeping history via table versioning and checkpoints. The architecture implements bronze/silver/gold medallion layers, uses a foreachBatch loop with merge into (upsert) to update a single changed row among batches, and supports switching between continuous streaming and scheduled runs via triggerOnce. It demonstrates reliable, low-latency updates without rewriting whole files.
AI-written summary · about
chapters (12)
- 0:00Introduction to incremental ETL
- 1:42Why incremental ETL matters
- 8:10Advantages of incremental ETL
- 12:05Ingest in incremental ETL
- 14:34Structured Streaming for ETL
- 17:27Continuous vs scheduled processing
- 19:12Delta Lake for updates and deletes
- 21:01Streaming between Delta tables
- 22:23Schema evolution in Delta
- 24:26Example of incremental ETL
- 27:36Upserting data in real time
- 29:41Q&A and closing remarks
related talks
50mIntroduction to Databricks Delta Live Tables
22mReliable data engineering made easy
21mBuilding Data Integration Services In Real Time
45mSimplify your ETL with Databricks Delta Lake
51mDeclarative ETL pipelines with Delta Live Tables
44mThe Changing Face of ETL: Event-Driven Architectures for Data Engineers
34mTales of Data Architecture Evolution
04mInterview
