Solution blueprint
Medallion data warehouse on an open lakehouse
A medallion data warehouse on DataNature lands raw data in Bronze, cleans and standardizes it in Silver, and publishes certified dimensional and fact tables in Gold, as open Delta Lake or Apache Iceberg tables. Trino serves fast SQL, the semantic layer defines KPIs once, and Atlas tracks lineage from report to source.
Updated
How it is built
- Land in Bronze
- Clean in Silver
- Publish Gold
- Define KPIs once
- Govern and audit
- Land in BronzeConnect loads sources as raw, immutable, timestamped and catalogued copies. Bronze is never deleted, so data can always be reprocessed.
- Clean in Silverdbt models deduplicate, handle nulls, check referential integrity and apply business rules.
- Publish GoldDimensional and fact tables, certified and version-controlled, optimized for analytics.
- Define KPIs onceThe semantic layer exposes certified views and KPIs to BI, Voir and third-party tools.
- Govern and auditEvery dbt run writes lineage to Atlas. Time travel makes reports reproducible.
- Connect
- Batch, incremental and full loads from 200+ sources into Bronze
- Data Engineering workbench
- dbt and Spark transformations from Bronze to Gold
- Lakehouse
- Delta Lake and Apache Iceberg tables with ACID, time travel and schema evolution
- SQL warehouse
- Massively parallel SQL with Trino federation
- Semantic Layer
- Certified views and KPIs for BI, Voir and apps
- Atlas
- Catalog, RBAC, PII masking, lineage and audit
On this page
Why build a warehouse on a lakehouse?
Because you get one copy of data. The warehouse runs directly on open Delta or Iceberg tables, so there is no separate warehouse to load, no data movement, and no lock-in.
What goes in each layer?
- Bronze: raw, immutable copies of every source, timestamped and partitioned.
- Silver: cleansed, deduplicated, standardized and validated against business rules.
- Gold: business-ready dimensional and fact tables, certified and versioned.
How do BI tools and agents use it?
Through the semantic layer. Power BI, Tableau, DataNature BI and Voir all query certified views and KPIs, so every number matches.
How long does a migration take?
It depends on the number of sources and reports. Dlytica Consulting scopes it in a short assessment and runs old and new in parallel, reconciling with Atlas lineage before cutover.
Common questions
What is the medallion architecture?
Bronze holds raw data, Silver cleaned data and Gold business-ready tables. See medallion architecture explained.
Do we still need a separate data warehouse?
No. The SQL warehouse runs directly on open lakehouse tables, so there is one copy of data.
Is a lakehouse overkill for small data?
Sometimes. See the honest guide for small teams.
Implementation details
- Land sources in Bronze with Connect: Oracle, SQL Server, MySQL and PostgreSQL over JDBC into
lakehouse.bronze_<source>.<table>. Use full loads for reference tables, Full → Incremental for large transactional tables, and a bookmark column that changes on every update. - Partition only large tables, by month for long histories; set partitioning before deploy.
- Model Silver in dbt on the Spark target: de-duplicate to the latest row per key, cast types, and add
not_nullanduniquetests. - Model Gold marts per domain (finance, customer, risk) as facts and dimensions, with
relationshipstests and incremental materialization for large facts. - Define certified KPIs as semantic-layer cubes over Gold, and materialize the busiest ones in DN Warehouse.
- Schedule one Ingest + Transform job per domain: pipeline → dbt Silver → dbt Gold → Refresh cubes, in your time zone.
- Apply governance in Atlas: groups mirroring the organization, PII masks in Bronze and Silver too, row filters on Gold.
- Reconcile Gold totals against the legacy warehouse per period before switching reports over.
Platform components in this blueprint
Learn more about each DataNature product and module mentioned here.
See it on your own data.
Book a demoDemos and quotes are handled by Dlytica, the company behind DataNature.