Forum Discussion

SamyAbdul's avatar
SamyAbdul
Frequent Visitor
2 days ago
Solved

Lakehouse Build

Hi Experts , we are developing bronze layer as of now , so as per Microsoft Fabric's best practices , I have suggested the having lh_bronze, lh_silver and warehouse_gold.  The client was of the opini...
  • ShivekMaharaj's avatar
    2 days ago

    Hi SamyAbdul​,

    Your client’s one-lakehouse approach can work technically, especially now that Fabric Lakehouse supports schemas, but I would still prefer separate layers for a production medallion design unless there is a strong reason to combine them.

    Microsoft’s medallion architecture guidance for Fabric recommends keeping Bronze, Silver and Gold as separate layers, typically in separate Lakehouses/Warehouses.

    A common pattern would be:

    Bronze Lakehouse
    → raw/source-aligned data
    
    Silver Lakehouse
    → cleansed, standardized, deduplicated and conformed data
    
    Gold Warehouse or Lakehouse
    → business-ready facts, dimensions and aggregates

    The main advantage is not really performance - it is operational separation. Separate layers make permissions, ownership, deployment, troubleshooting, reprocessing and lifecycle management much clearer.

    For Gold, I would also consider a Warehouse if the main consumers are Power BI and SQL users. Microsoft explicitly documents Bronze/Silver in Lakehouse and Gold in Warehouse as one of the supported medallion deployment patterns.

    In terms of cost, having three items does not automatically mean three times the cost. Fabric consumption is driven more by storage, transformation workload, query activity and CU usage than by the number of Lakehouse objects themselves. The same data processed in the same way will generally have a similar storage footprint, although different architectures can change how much compute is consumed during processing.

    A single Lakehouse with bronze/silver/gold schemas is still valid, and Microsoft also shows schema-based patterns in current Lakehouse guidance. I would mainly choose that for smaller or simpler solutions where governance and operational separation are less important.

    So for a scalable enterprise design, I would stay with your lh_bronze / lh_silver / warehouse_gold approach unless the client has a specific requirement that makes a single Lakehouse materially simpler.

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.