It might sound simple but choosing the right workspace strategy it crucial to a successful implementation of Data Engineering solution in Microsoft Fabric. Should you add everything in one workspace, have one workspace per stage, one workspace per workload or something entirely different?

There are few things which will impact your workspace strategy such as size and composition of your development team, DevOps strategy and workload/data isolation. Some of it is because of the way Fabric works while others are due to security restrictions.

In this session we are going to go through each one of them and analyze the impact of it on your workspace strategy.

We will take an outset in the popular Medallion architecture as most teams use some version of that when building lakehouses in Fabric.

Using the Medallion architecture we will demonstrate how different things impact the workspace strategy and show how what ways you can use either work around or overcome the issues.

At the end of this session the audience will understand better what challenges there are in Fabric when it comes to workspace strategy and what possible solutions there are. There is no such thing as one size fits all but starting correctly can heavily reduce re-work or workaround at later stages.