Workspace Architecture

Hi tim_goodsell 

I have used this approach and works pretty well 

main benefits you will have with approahc:

Keeping code seperate from the data workspaces has been really helpfull. Main benifits I’ve seen so far:
Access is way easier to manage - engineers dont need direct access to prod lakehouses and business users consuming gold data dont need to see all the notebook code. Makes permissons much cleaner.

Capacity isolation is a big one - data engineering jobs cant impact reporting performace anymore since there on diffrent capacities. Before we had issues with noisy neighbours.

CI/CD just works better with this setup - deployment piplines need seperate workspaces anyway so it fits naturally.

We use OneLake shortcuts to connect everthing across workspaces without duplicating data which is nice.