DESCRIPTION 📄
During the last months, we have heard a lot about Microsoft Fabric and how it will change the analytical landscape. How it will help solve the most demanding analytical challenges.
It has become simple to create a lakehouse in seconds, or two, or a hundred. How will we organize our Fabric workspace? Do we have one workspace with three lakehouses (bronze, silver, and gold), or do we have three workspaces? Next to the number of workspaces, what about the capacities? Will a solution “own” multiple capacities, or only one or two, and share compute power with other teams, utilizing the idea of the share economy? Here, I want to share some early thoughts, including aspects of data architectures like data mesh and data fabric.
GUEST BIO (Tom Martens) 👤
Thomas "Tom" Martens has been awarded as an MSFT Data Platform MVP and works as Solution Architect at Munich Re. For 20+ years, Tom delivers Business Intelligence, Data Warehousing, and Analytics solutions. His current interest is in data visualization and applying analytical methods to small and large amounts of data, next to providing the Power BI Platform to users for tackling analytical challenges. Tom is a regular speaker at international conferences and user meetings. Tom is the co-author of the book "Pro DAX with Power BI."
