Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
Check it out now!Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hi,
I've known that in Fabric it is possible to have only one OneLake for the entire organization, but should it possible to have an OneLake for each layer of the medallion architecture (bronze, silver and gold layers) or is it a senseless idea?
Thanks
Solved! Go to Solution.
Hi @pmscorca
Thanks for using Microsoft Fabric Community.
Microsoft Fabric's medallion architecture leverages a single OneLake for all data tiers (bronze, silver, gold). This simplifies data management and avoids the overhead of maintaining separate OneLakes for each layer. OneLake is designed to be a single, unified, logical data lake for your entire organization. It offers functionalities like data categorization using domains and workspaces, which makes it suitable to handle data at various stages of refinement. The idea behind OneLake is to remove silos, reduce management effort, and minimize data movement and duplication.
Benefits of a Single OneLake:
Why Multiple OneLakes Might Not Be Ideal:
Using a single OneLake and logically organizing it to reflect the medallion architecture is a sensible and efficient approach. It leverages the strengths of OneLake in terms of integration, governance, and management while still adhering to the principles of the medallion architecture. This method ensures streamlined operations and cost-effectiveness while maintaining clear separation and organization of data at different processing stages.
I hope this information helps. Please do let us know if you have any further queries.
Thank you.
Hi @pmscorca
Thanks for using Microsoft Fabric Community.
Microsoft Fabric's medallion architecture leverages a single OneLake for all data tiers (bronze, silver, gold). This simplifies data management and avoids the overhead of maintaining separate OneLakes for each layer. OneLake is designed to be a single, unified, logical data lake for your entire organization. It offers functionalities like data categorization using domains and workspaces, which makes it suitable to handle data at various stages of refinement. The idea behind OneLake is to remove silos, reduce management effort, and minimize data movement and duplication.
Benefits of a Single OneLake:
Why Multiple OneLakes Might Not Be Ideal:
Using a single OneLake and logically organizing it to reflect the medallion architecture is a sensible and efficient approach. It leverages the strengths of OneLake in terms of integration, governance, and management while still adhering to the principles of the medallion architecture. This method ensures streamlined operations and cost-effectiveness while maintaining clear separation and organization of data at different processing stages.
I hope this information helps. Please do let us know if you have any further queries.
Thank you.
Hi @pmscorca
Glad that you query got resolved.
Please continue using Fabric Community for further queries.
Thanks.
User | Count |
---|---|
26 | |
14 | |
9 | |
9 | |
4 |
User | Count |
---|---|
32 | |
29 | |
21 | |
17 | |
6 |