Forum Discussion
Folders Structures in workspace
- 13 days ago
HI reddyr2502 ,
It depends on your organization size, for example if your organization is small and there is less potential of future growth, then it is recommended that keep all artifacts in single workspace.
However, i would strongly recommend creating separate workspaces as mentioned under:
WS_Dev ----> WS_UAT ----> WS_Prod
Now in Dev Workspace you keep all artifacts in the folders like for an example for Lakehouse , use Lakehouse and for notebooks use Notebooks and so on.
Deployment Pipeline:
Now everything that should move from Dev to UAT & UAT to PROD must be through Deployment Pipelines, a built in feature in fabric premium portal. Thanks
Reference: MicrosoftIf this helps, ✓ Mark as Kudos | Help Other
Hi reddyr2502,
It really depends on how you work and how you've structured your environment.
I've seen one folder per source system before, and then inside that are subfolders for bronze, silver, and gold components.
I've also seen the root folders be bronze, silver, and gold, and then in each of those are subfolders for each system.
My environment is metadata driven for bronze and silver layers, so there's nothing system specific at that level, I have a folder for some shared functions that I've abstracted away from the main notebooks so they can be reused across layers, and then I have a single notebook for bronze and a single notebook for silver that will read from the metadata tables and load what needs to be loaded.
Then at my gold layer I have a top level folder for gold, and inside I have a folder for each resulting data product.