25 editable reference diagrams
Data Engineering Architecture Diagrams
Data engineering architecture diagrams connect operational sources with ingestion, transformation, governed storage and consumers. Compare lakehouse, warehouse, batch and change-data-capture designs around freshness and data ownership.
Trace one record through validation, deduplication and publication. Specify how schema evolution, backfills and late data affect downstream models. A pipeline is useful only when teams can explain whether a missing result comes from the source, a quality gate or the serving layer.
Choose a diagram for your design question
Open a reference to inspect its component flow and trade-offs, then adapt it in the browser-local editor. Manual editing does not require login; AI generation and account storage do.

Data pipeline architecture
Separate raw evidence from transformed outputs.
6 components · 5 connections
Explore data pipeline architecture →
ETL pipeline architecture
Validate data before loading serving tables.
6 components · 5 connections
Explore etl pipeline architecture →
ELT pipeline architecture
Retain raw data for repeatable transformations.
5 components · 4 connections
Explore elt pipeline architecture →
Batch data processing architecture
Track completeness by batch identity.
6 components · 5 connections
Explore batch data processing architecture →
Real time data pipeline architecture
Define acceptable freshness and late-arrival behavior.
6 components · 5 connections
Explore real time data pipeline architecture →
Data lake architecture
Govern data by ownership and sensitivity.
6 components · 5 connections
Explore data lake architecture →
Data warehouse architecture
Model analytical grain before building facts.
5 components · 4 connections
Explore data warehouse architecture →
Data lakehouse architecture
Open files still need transactional table metadata.
6 components · 5 connections
Explore data lakehouse architecture →
Medallion Lakehouse Data Pipeline
Retain Bronze source fidelity
8 components · 8 connections
Explore medallion lakehouse data pipeline →
Bronze silver gold data architecture
Make each quality promotion reproducible.
6 components · 5 connections
Explore bronze silver gold data architecture →
Modern data stack architecture
Assign ownership across separately managed tools.
6 components · 5 connections
Explore modern data stack architecture →
Data mesh architecture
Federate ownership without abandoning shared standards.
5 components · 4 connections
Explore data mesh architecture →
Data fabric architecture
Metadata automation requires trustworthy source contracts.
6 components · 5 connections
Explore data fabric architecture →
Data ingestion architecture
Do not confuse receipt with successful validation.
6 components · 5 connections
Explore data ingestion architecture →
Change data capture architecture
Handle snapshots and log changes consistently.
7 components · 5 connections
Explore change data capture architecture →
Data quality monitoring architecture
Tie quality rules to consumer requirements.
7 components · 5 connections
Explore data quality monitoring architecture →
Data lineage architecture
Track transformation versions as well as table names.
5 components · 4 connections
Explore data lineage architecture →
Data catalog architecture
Keep discoverability separate from access grants.
7 components · 6 connections
Explore data catalog architecture →
Master data management architecture
Record survivorship decisions and source provenance.
5 components · 4 connections
Explore master data management architecture →
Data governance architecture
Policies need enforceable owners and evidence.
7 components · 5 connections
Explore data governance architecture →
Reverse ETL architecture
Prevent repeated writes and unintended audience exposure.
6 components · 5 connections
Explore reverse etl architecture →
Data migration architecture
Verify cutover consistency before redirecting writes.
7 components · 6 connections
Explore data migration architecture →
Data reconciliation architecture
Compare like-for-like periods and record identities.
6 components · 5 connections
Explore data reconciliation architecture →
Data observability architecture
Alert on meaningful consumer impact.
6 components · 5 connections
Explore data observability architecture →
Data sharing platform architecture
Sharing contracts must cover deletion and revocation.
7 components · 5 connections
Explore data sharing platform architecture →