Skip to content

Project

Lakebase

Databricks' managed serverless Postgres database service, with autoscaling computes, storage separate from compute, and instant branching.

Known aliases

  • Databricks Lakebase
  • Lakebase Postgres

Current stories

buildOne report1 publisher

Databricks isolates app and database limits in its Lakebase Search sizing test

Databricks tests Lakebase Search on 1M to 4M rows, using a 23,000-row internal app as its baseline. A search request touches two computes, the app's and the database's, and either one can set the limit.

Publishers:databricks.com

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives65
Confidence55
buildOne report1 publisher

Lakebase swaps Postgres copy-and-replay restores for a branch at a timestamp

Databricks says Lakebase restores Postgres in seconds even at 100 TB by creating a branch at a timestamp. The figure times branch creation, so it matches a finished RDS restore only if that branch serves production reads at once.

Publishers:databricks.com

Reality

Evidence30
Adoption
Not scored
Hype gap+45
Incentives85
Confidence40
buildOne report1 publisher

Databricks raises Lakebase's 1 GB shared buffers cap to most of the machine's memory

Hot pages on large fixed-size Lakebase computes now sit in Postgres shared buffers backed by huge pages instead of falling through to the local file cache, and Databricks measures up to about 2x throughput.

Publishers:databricks.com neon.tech

Reality

Evidence55
Adoption40
Hype gap+15
Incentives85
Confidence60
buildOne report1 publisher

Databricks moves feature serving to streaming, and the 200ms is measured to the write

A p99 of 200 milliseconds from Kafka to the online store beats batch cadence by a wide margin. It also stops before your model reads the feature.

Publishers:databricks.com

Reality

Evidence34
Adoption
Not scored
Hype gap+34
Incentives88
Confidence41