Forum Discussion
arpost
Post Prodigy
Post ProdigyHow do Dev/Test/Prod workspaces fit into Fabric architecture?
Greetings, community. I'm continuing to explore Fabric and identify how to use the different components especially in relation to traditional ALM with Dev/Test/Production workspaces. Microsoft has ta...
- 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.
Consider Dev/Test/Prod and Bronze/Silver/Gold as separate things. B/S/G represents transformations done on your data, whilst D/T/P are stages in safely making changes to those transformations and bringing new ones into existence.
There is going to be a degree of replication of data across all these areas. We will only replicate across D/T/P what we have responsibility to create, any data set that we only read we access the live/production data for Dev & Test. We will try to minimise the replication of our own data sets in Dev & Test (how to best to this is something we are currently investigating - poss ADF only what we need to Dev & Test)