cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

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
Contributor

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 ?Databricks non-prod workspace set up options

1 ACCEPTED SOLUTION

Accepted Solutions

pvignesh92
Honored Contributor

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

  1. To isolate and best manage your CICD pipelines,
  2. To provide access controls at the workspace level for different users . Ex more privileges in Dev vs restricted privileges in Prod workspace
  3. 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.

View solution in original post

2 REPLIES 2

pvignesh92
Honored Contributor

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

  1. To isolate and best manage your CICD pipelines,
  2. To provide access controls at the workspace level for different users . Ex more privileges in Dev vs restricted privileges in Prod workspace
  3. 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.

Avvar2022
Contributor

Thank you. This helps.