Forum Discussion
Solved
How 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.
Hello
The Dev/Test/Prod workspaces in Fabric architecture are essential to the ALM process. Fabric's medallion-style approach has the potential to combine several artifacts into a single workspace, whereas conventionally, each workspace (Dev, Test, and Production) houses a version of each artifact.
In this case, the data would move within the same workspace from Bronze to Gold. This does not, however, imply that everything in Test and Production must be redone. Because of Fabric's architecture, redundant processes can be avoided and data pipelines may be managed effectively.
Regards
Nisha Marshall