Azure Databricks architecture overview
This article provides a high-level overview of Azure Databricks architecture, including its enterprise architecture, in combination with Azure.
High-level architecture
Azure Databricks operates out of a control plane and a compute plane.
- The control plane includes the backend services that Azure Databricks manages in your Azure Databricks account. The web application is in the control plane.
- The compute plane is where your data is processed. There are two types of compute planes depending on the compute that you are using.
- For serverless compute, the serverless compute resources run in a serverless compute plane in your Azure Databricks account.
- For classic Azure Databricks compute, the compute resources are in your Azure subscription in what is called the classic compute plane. This refers to the network in your Azure subscription and its resources.
The following diagram describes the overall Azure Databricks architecture.
Serverless compute plane
In the serverless compute plane, Azure Databricks compute resources run in a compute layer within your Azure Databricks account. Azure Databricks creates a serverless compute plane in the same Azure region as your workspace’s classic compute plane.
To protect customer data within the serverless compute plane, serverless compute runs within a network boundary for the workspace, with various layers of security to isolate different Azure Databricks customer workspaces and additional network controls between clusters of the same customer.
To learn more about networking in the serverless compute plane, Serverless compute plane networking.
Classic compute plane
In the classic compute plane, Azure Databricks compute resources run in your Azure subscription. New compute resources are created within each workspace’s virtual network in the customer’s Azure subscription.
A classic compute plane has natural isolation because it runs in each customer’s own Azure subscription. To learn more about networking in the classic compute plane, see Classic compute plane networking.
For regional support, see Azure Databricks regions.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for