Forum Discussion
Post ProdigyHow do Dev/Test/Prod workspaces fit into Fabric architecture?
- yes and even creating new files in lakehouses. we could say that each line could be "duplicated" as many layers you have in your architecture. in reailty you need to add layers since your data isn't ready for users consumption yet therefore it's not exactly duplicated and equal to the previous layer. in our projects we tipically hide everything with the exception of "gold/final" layer to final users, therefore it's very close to "one copy". by the way it's pratical vs theory.
- in my opinion every environment "DEV/TEST/UAT, PROD" should be considered as an atomic and isolated ecosystem with itsown artifacts (lakehouses, warehouses..) and permissions that doesn't communicate with other environments. you're going to duplicate data among different environments but if you are in "test" you shouldn't see what is "prod". again practical vs theory.
Hi arpost ,
Thanks for using Fabric Community.
This is an architecture question and the answer is "it depends" on requirements. Choice of architecture/layout of workspaces could be driven by cost, performance, org structure, isolation/governance boundary requirements etc.
From product perspective, Fabric is flexible and building blocks (workspaces and items) can be laid out in different ways to meet business requirements. Common patterns which we have seen thus far:
Pattern 1: Separate workspace and separate Fabric Items (WH, LH) for Bronze, Silver and Gold layers.
From ALM perspective, in the current release of Fabric, you would use separate deployment pipelines for Bronze, Silver and Gold layers which are each represented by a separate workspace.
Bronze Deployment pipeline: [WS <dev-bronze>] -> [WS <test-bronze>] -> [WS <prod-bronze>]
Silver Deployment pipeline: [WS <dev-silver>] -> [WS <test-silver>] -> [WS <prod-silver>]
Gold Deployment pipeline: [WS <dev-gold>] -> [WS <test-gold>] -> [WS <prod-gold>]
Pattern 2: Single workspace with separate LH or WH for Bronze, Silver and Gold layers.
Further reading which I would recommend to help shape your decision:
Implement medallion lakehouse architecture in Microsoft Fabric - Microsoft Fabric | Microsoft Learn
Microsoft Fabric adoption roadmap - Power BI | Microsoft Learn
Deployment patterns for Microsoft Fabric - Azure Architecture Center | Microsoft Learn
Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn
Hope this is helpful.
Hi arpost ,
We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help .
Thanks