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.
arpostPost Prodigy
Post ProdigyThank you both for your replies, Anonymous and R1k91. That's very helpful. Two additional questions:
- Am I right in thinking there will still be duplication when doing things like inserts into data warehouses?
- If an organization is wanting to have a centralized data repository but then pull that data into Dev/Test/Prod workflows, would the idea be that you have a "Data Repository" (perhaps a separate lakehouse) and then shortcut that into each workspace?
Trying to figure out how to work toward that OneCopy vision and ensure we don't end up just storing double/triple/quadruple the exact same data across numerous workspaces.
R1k91Super User
- 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 ,
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