Forum Discussion

ndamoi's avatar
ndamoi
Frequent Visitor
1 year ago
Solved

Workspace & Medallion Architecture Design with Centralised Logic on Bronze and Silver

Hello all, I hope you're doing well! This is my first post here, so please be gentle 😊 I'm a junior data engineer/scientist working at a small-to-midsized company, and I'm currently leading the cre...
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi ndamoi ,

    Thank you for reaching out to the Microsoft fabric community forum.

     

    To answer your first question: yes, keeping the bronze and silver layers centralized is a common and smart setup, especially for small or mid-sized companies. It helps you keep your data consistent, makes things easier to manage, and avoids repeating the same transformation logic in different places which is great when different teams use the same cleaned data.

     

    Your approach of using department-specific workspaces with their own Gold layer and connecting them to shared Silver tables using shortcuts is a solid and flexible solution. It gives each team the freedom to add their own business logic without changing the core data. This setup is actually supported in Microsoft Fabric through Lakehouse Shortcuts, which are designed exactly for sharing data between workspaces without copying it.

     

    Your separation of environments into Dev, Test, and Prod, along with connecting them to Git branches, demonstrates good planning for long-term stability. While full Git integration in Fabric is still being developed, using repositories and deployment pipelines as a temporary solution is effective and will position you well as more automation features become available.

     

    Your approach to access control restricting Bronze and Silver to yourself while granting departments access to Gold lakehouses and Power BI workspaces follows current data ownership practices, balancing centralized engineering with decentralized consumption. This setup supports both data quality and governance, while allowing for secure self-service analytics. The main areas to watch are the complexity from shortcuts, metadata documentation, and auditing pipeline runs. It would help to clearly document shortcut usage and use consistent naming to make dependencies easier to follow. As your platform grows, consider adding simple operational logs or dashboards to monitor data freshness and ownership.

     

    Overall, your setup follows good design practices and matches how Microsoft Fabric is meant to be used. It puts you in a great position to grow and manage things smoothly as your data needs increase.

    Hope this helps. Please feel free to reach out for further assistance.

     

    Thank you.