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.
Super UserIMHO Bronze/Silver/Gold is a transformation pattern and it's applied inside a project.
a project could be in dev, test or production environments. therefore yes you're going to copy data in multiple environments (but you could decide to have subset of data in dev and test for example).
we put all the layers inside one workspace and then we'll create a workspace per environment.
you could split layers in different workspaces but you'll need to create workspaces per environment also.
3 wrksp dev (gold siver and bronze) 3 wrksp test 3 wrksp prod = 9 wkrsp that is much more complicated to manage even from a deployment perspective.
having different environments with all the layers will duplicate data across workspaces but "one copy" principle will be true for users that should only see the production one.
moreover you can say "one copy" principle is true "at environment level" because in test environment there'll be only one gold layer, as one silver and so on.