Forum Discussion

reddyr2502's avatar
reddyr2502
Regular Visitor
1 month ago
Solved

Folders Structures in workspace

Hi, I am the only person managing data analytics at a startup. We currently use a single Microsoft Fabric workspace for our Bronze, Silver, and Gold data layers. What is the best way to organize an...
data engineering
  • Murtaza_Ghafoor's avatar
    Murtaza_Ghafoor
    1 month 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: Microsoft


      If this helps, ✓ Mark as Kudos | Help Other



svenchio's avatar
svenchio
Icon for Super User rankSuper User
1 month ago

Hi  @reddyr2502 , risking to sound a bit cliche, but the best way to organize fabric items is the one that best fit with  your development process, understanding and best support your governance/security requirements and spaceman127 and tayloramy correctly indicated, in this context, I guess the best I can offer is how I organize my workspace and items, and in a way, give you the reason why and, if you like it, you can implement and improve upon it 😉

If create my workspace using the concept of solutions, that is, all workspaces contain the items that contribute to a solution, and using a naming convention have one workspace per environment like this. 

Within the solution coordinator, I have folder for each data product within a solution, in this case, the workspace coordinator is meant to coordinate & monitor my fabric ecosystem, within, I have 2 data products, observatory that collects events and inventory of fabric and operations that orchestrate the execution of several data pipelines, hence, each has its folder and a lakehouse that supports data for the whole solution.  

And zooming to a very specific feature of my observatory data product, I have this folder fabric-inventory witch is a very specific feature that extracts data using a medallion architecture, I use a naming convention as follow. 

And of course, the pipeline orchestrate the execution of my medallion stages. 

Perhaps you want to use this approach, it has worked for me pretty well thus far!  😁 Hope at least you find it interesting and useful to discuss and come up with your very own interpretation. 

Hope for the best mate, and reach out for any questions .... mark as solution and give us a thumbs up!