Skip to main content

06. Databricks Workspace

A Databricks workspace is the collaborative environment where teams develop and run data, analytics, and AI workloads.

Workspace mental model​

Databricks Account
   │
   ├── Workspace A
   ├── Workspace B
   └── Workspace C
          │
          ├── Notebooks
          ├── Jobs
          ├── Compute
          └── SQL assets

The workspace is not the same thing as the durable data layer. Governed data can be stored in cloud storage and managed through Unity Catalog.

Workspace vs account​

The account is the higher-level administrative scope.

A workspace is an environment used by teams and workloads.

Enterprise organizations may create separate workspaces for development, testing, production, regions, regulatory boundaries, or specialized workloads.

Do not create workspaces casually​

A workspace can introduce network configuration, identity configuration, compute policies, logging, monitoring, CI/CD, and governance administration.

Workspace and Unity Catalog​

Unity Catalog provides governance across workspaces connected to the relevant metastore. Current Databricks guidance favors Unity Catalog managed tables and governed access patterns over legacy storage access approaches.

Production checklist​

Before creating a production workspace, define:

  • Cloud region.
  • Networking.
  • Identity.
  • Unity Catalog.
  • Catalog strategy.
  • Compute policies.
  • Secrets.
  • Logging.
  • Monitoring.
  • CI/CD.
  • Disaster recovery.
  • Cost controls.

Key takeaway​

Think of a workspace as a controlled execution and collaboration boundary, not as “the database.”

Next​

Continue with the next topic in 01. Databricks Foundations.