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



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

Hi reddyr2502​ ,

Actually, the organization is completely flexible. In the end, it really depends on how you have structured your project and what feels most comfortable for you.

Personally, I like to separate everything by type and keep the workspace well organized. For example, these are the folders I use:

  • 00_Tools
  • 01_Ingestion
  • 02_Processing
  • 03_Semantics
  • 99_Monitoring

However, I have also used a structure based on Bronze, Silver, and Gold, with different artifacts organized within each layer, such as Notebooks and Lakehouses, and even a separate folder for reports.

At the end of the day, there is no single correct structure. The important thing is to work in a way that feels comfortable for you while also making it intuitive and easy to understand for anyone else who might join the project later.

If this helped, please consider giving it a Like. If it solved your issue, please mark it as the Accepted Solution to help others facing the same problem.

Thanks