Forum Discussion

JDay98's avatar
JDay98
Frequent Visitor
1 year ago
Solved

Architecture Design in Fabric

I am new to Data Engineering and Fabric, I am trying to design an architecture for my organization. My goal is to have a centralized data repository that allows high level of data governance, but not...
data engineering
lakehouse
  • Srisakthi's avatar
    Srisakthi
    1 year ago

    Hi JDay98 ,

     

    There are few points based on my understanding, Decoupled architecture helps in maintaining data access to restricted set of people.

    1. You can leverage Domain based in case if you want to separate it out at higher level by departments

    2. Lakehouse Schema is still in Preview , so some features will not function as expected. Better to avoid it.

    3. Have you explored One Lake Security? 

    4. With Fabric Deployment Pipeline you cannot copy data.

     

    Regards,

    Srisakthi

Vinodh247's avatar
Vinodh247
Super User
1 year ago

 

  • Use Option 2 (Department-wise Lakehouse) for ease of access control, lower overhead, and modular ownership.

  • Limit the access in Department Workspaces to only relevant Gold tables via Shortcuts (good for governance).

  • Use Data Pipelines or Notebooks to move data across stages (Bronze > Silver > Gold) within the same lakehouse.

  • Use Deployment Pipelines to promote your entire workspace (including lakehouse artifacts and PBI reports) from Dev to Prod.