Forum Discussion
Folders Structures in workspace
- 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: MicrosoftIf this helps, ✓ Mark as Kudos | Help Other
Hi reddyr2502 ,
As stated by multiple members above, the decision is purely on your business requirement and your focus area. When we say Business requirement we mean :
- Your security consideration
- Your access model
- Your data segregation models
- User level / department level adoption model of the solution etc.
So, you can continue with whatever you are building as it is already align to your business requirement but yes there are few area where I would recommend you keep and on like :
Prefix Maning conventions eg: PL_ = Pipeline / NB_ = Notebook / DF_ = Dataflow /LH_ = Lakehouse/ WH_ = Warehouse /SM_ = Semantic Model /RP_ = Report
As I see you can follow the below architecture for reference
as for the Fabirc deployment we have multiple options/ frameworks as:
Hope this give you the clarity to make your choice