Product area

Lakebase

Lakebase, the managed Postgres inside Databricks: projects and branches, computes that scale to zero, connecting and authenticating, synced tables from Unity Catalog, changes back into Delta, and apps built on it.

Concepts

9 in this area
  1. 1Lakebase, the Postgres inside DatabricksLakebase is a managed PostgreSQL database that lives inside Databricks. You get a real Postgres — the same wire protocol, the same SQL, the same drivers and tools — without running a server, patching it, sizing its disks or arranging its backups. It sits next…
  2. 2Projects, branches and point-in-time restoreA project is the top-level container of Lakebase: one per application or team, created in the workspace's region. Inside it, the unit you actually work with is the branch. A branch is a complete, isolated Postgres environment — its own data, its own computes…
  3. 3Computes, autoscaling, scale-to-zero and high availabilityA compute is the running Postgres process that serves a branch. In the API it is called an endpoint, and there are two kinds:
  4. 4Connecting to Lakebase, roles and permissionsA Lakebase compute is reached like any Postgres server: a host, port 5432, a database, a user and a password, over TLS. What is particular to Lakebase is where the password comes from and what the user is.
  5. 5Synced tables, from Unity Catalog into PostgresA synced table is a copy of a Unity Catalog table inside a Lakebase database, kept current by Databricks and read-only on the Postgres side. The source can be a managed or external Delta table, an Iceberg table, a view or a materialized view. Creating one…
  6. 6Lakebase change data feed, from Postgres into DeltaThe Lakebase change data feed records the changes made to Postgres tables in a Lakebase database as rows in Unity Catalog managed Delta tables. For a Postgres table orders, every insert, update and delete arrives in a history table named lbordershistory, with…
  7. 7Registering a Lakebase database in Unity CatalogA Lakebase database can be registered as a catalog in Unity Catalog. The catalog mirrors one Postgres database: its schemas become Unity Catalog schemas and its tables become tables you can find in Catalog Explorer, grant on, trace in lineage and query with…
  8. 8The Data API and Postgres extensionsTwo ways of getting more out of the same Postgres without adding a server:
  9. 9Lakebase behind an app, an agent or a feature storeA Databricks App — a Dash, Flask or Streamlit application running on the platform — gets a Lakebase database by adding it as a resource, the same way it gets a warehouse or a model endpoint. You pick the project, the branch and the database; the platform does…

News

No news for this area.

Resources

No external resources linked yet.