Concepts for Databrickss
Databricks concepts are the ideas behind the platform: the lakehouse model, workspaces, clusters and serverless compute, notebooks, and Delta Lake as the table layer on cloud storage. This unit sits at the start of the roadmap because every later topic, from ingestion to governance, builds on how these parts fit together.
Stage: Platform · Part of the Databricks roadmap · Last reviewed 19 November 2026
What to learn in Concepts
- Explain how a lakehouse differs from a data lake and a data warehouse
- Create a notebook, attach compute and run a cell against a table
- Describe how Delta Lake adds ACID transactions to files in object storage
- Use DESCRIBE HISTORY and time travel to read an earlier table version
- Tell apart a workspace, a catalog and a compute resource
Concepts interview questions
What problem does Delta Lake solve compared with plain Parquet files?
Plain Parquet files have no transaction log, so concurrent writes can leave readers with partial data and you cannot safely update or delete rows. Delta Lake adds a transaction log over Parquet, giving atomic commits, schema enforcement, updates, deletes and time travel.
What is a lakehouse and why did Databricks promote it?
A lakehouse keeps data in open formats on cheap object storage but adds warehouse features such as transactions, SQL performance and governance. It avoids copying data between a lake for data science and a warehouse for BI, which cuts duplication and stale copies.
Where Concepts fits in the Databricks roadmap
Concepts belongs to the Platform stage (beginner level). Lakehouse basics.
Back to the full Databricks roadmap