I kept getting the same interview question, "explain the Databricks architecture", and most answers are a wall of text. So I drew it.
The crisp answer: Databricks manages the control plane (web app, job scheduler, notebook metadata). Your compute runs in the compute plane, classic in your own cloud account or serverless in the Databricks account. Data stays in your storage as Delta tables, and Unity Catalog governs all of it. When you run a notebook, the control plane sends the work to the compute plane and the data never leaves your account.
Full animated walkthrough (2 min): https://youtu.be/B5iHmoYgnqY
It is episode 1 of a 27-part series checked against the current docs, so if I got something wrong, tell me and I will fix it.
