topic I am new to data bricks. setting up Workspace for NON-prod environment Separate workspaces for DEV, QA or Just one work space for NON-prod ? in Data Engineering

I am new to data bricks. setting up Workspace for NON-prod environment Separate workspaces for DEV, QA or Just one work space for NON-prod ?

Avvar2022 — Sun, 26 Mar 2023 14:52:01 GMT

What i learned based on learning materials, documents, etc.. For data bricks it is a good practice to set up 1 non-prod workspace but separate clusters for Dev, QA, SIT, etc.

Is it best practice to set up only 1 NON-PROD Workspace instead of separate workspaces DEV, QA, UAT, etc..

Which option would be a best practice Option 1 Or Option 2 ?

Re: I am new to data bricks. setting up Workspace for NON-prod environment Separate workspaces for DEV, QA or Just one work space for NON-prod ?

pvignesh92 — Mon, 27 Mar 2023 10:49:46 GMT

@Ashok Zubrewar Hi. IMHO, the best practice is Option2. This will help you

To isolate and best manage your CICD pipelines,
To provide access controls at the workspace level for different users . Ex more privileges in Dev vs restricted privileges in Prod workspace
To restrict access on Source data . Ex Dev data can be given access only to Dev cluster, Prod data can be given access only to Prod cluster.

Please see if this helps.

Re: I am new to data bricks. setting up Workspace for NON-prod environment Separate workspaces for DEV, QA or Just one work space for NON-prod ?

Avvar2022 — Wed, 29 Mar 2023 23:07:43 GMT

Thank you. This helps.