Fabric Medallion Architecture vs Traditional Architecture
Hello,
This might be a common scenario, where an organization is trying to use Fabric Medallion Architecture (Bronze, Silver, and/or Gold) instead of a traditional Architecture (Ex. Extract Staging DB and Data marts, that can be read from a reporting tool such as PBI). The question that often get asked is what advantage would Fabric provide that the traditional architecture doesn't. People often see that the Bronze /Silver/Gold layers in Fabric are equivalent to Extract/Stage/ DataMart in traditional architecture. What criteria can we highlight that Fabric Architecture will provide but not the traditional architecture. We are looking on some criteria never the less we are facing challenges:
Cost: Fabric seems the cheaper solution when compared to on-premise service or SAP BW/4HANA.
Earlier user engagement: although Fabric gives admin fabric the freedom to grant access on workspace levels or item levels, but we didn't find a best practices on where to engage different kinds of users in the Medallion Data flow.
What other criteria both from technical point of view and business point of view can help clarify the advantages of using Fabric.
Thanks
1
1 comment
Mohammad Eljawad
3
Fabric Medallion Architecture vs Traditional Architecture
Learn Microsoft Fabric
skool.com/microsoft-fabric
Helping passionate analysts, data engineers, data scientists (& more) to advance their careers on the Microsoft Fabric platform.
Leaderboard (30-day)
Powered by