Posts tagged "lakehouse"
- Six steps to your integration layer: from bronze to trusted gold
Bronze shipped and gold still isn't trusted. Here are six steps to the integration layer your medallion architecture is missing.
- Integration Layer: Pattern, Not Project
Data warehouse automation makes the integration layer a pattern, not a project: a catalog rendered through a Jinja template under one naming convention.
- The model is portable. The code is native.
Metadata-driven code generation should emit native code, not portable SQL. One governed model becomes a Databricks Asset Bundle; Snowflake and Fabric are next.
- No silver layer, no lakehouse
A medallion architecture with no defined silver layer is a dump house, not a lakehouse. Here is how to tell which one you built.
- You already own the stack
You already own the lakehouse, storage, and orchestration. The missing layer is data warehouse automation: business meaning in, Data Vault and workflows out.
- The Medallion Three-Body Problem
Without an agreed business model, bronze, silver, and gold drift apart: three suns pulling the medallion architecture into a three-body problem.
- Data Vault Needs New Rules for Lakehouse
Columnar storage, generated views, and AUTO CDC took over every load reason for Data Vault satellite splitting. What is left is business meaning.
- The Lakehouse Ended One Satellite Per Source
One satellite per source is a row-store habit. On Delta Lake width is cheap and joins are what you pay for: consolidate Data Vault satellites by meaning.