Forum Discussion
Fabric Workspace Architecture
As the use case has limited 1 Data Engineer, I would recommend it to go with Option 3 as it will have :
- Very easy to manage
- Everything in one place
- Easier monitoring
- Less clicking around and
- Faster development.
But i will also have few drawbacks like, can become messy if naming standards are poor, less security control etc.
Once the project mature and team expand you can gradually shift towards option-2 or Option-1
Approach 3 might be the easiest to manage long term. From what I understand, you most likely have a single capacity. You could create the required Lakehouses and Warehouses within one workspace and use security to provide the appropriate level of access to each team.
If each department’s data needs to be separated, using a separate schema for each department could be a good approach. However, we would need a little more detail about the requirements to recommend the right structure.
In most cases, I would not recommend giving users access to the entire workspace. Instead, provide access only to the specific Lakehouse or Warehouse they need.