Margin notes · Lakebase
Margin notes on Databricks, from the engineers.
What Databricks did, and what we read into it. Funding, pricing, products, renames, and what happens when the platform meets a client's production load. Written by the people doing the work, dated, with a position. RSS.
5 notes
Nothing matched that. Try a broader term, or clear the filter.
- Databricks Lakebase Postgres: GA on Google Cloud, and Cloud SQL Lakebase Postgres is generally available on Google Cloud. Five regions, an HA SLA, and what still keeps Cloud SQL in the picture. Read
- Databricks Lakebase Insights: per-project setup and what stopped Lakebase Insights now runs per project, on a schedule or on demand. Old observability schedules stopped, so what we would turn on and who should see it. Read
- MemCurrent on Databricks: what it is and when we'd use it MemCurrent is the design behind Databricks agent memory in Agent Bricks and Genie. How we would build agents on it, and where we would keep it out. Read
- Databricks LTAP Direct Writes in beta: faster synced table loads LTAP Direct Writes loads synced tables straight to storage, off the app's endpoint. What it covers, and the latency test we'd run before trusting it. Read
- Databricks Lakebase: why Databricks bought a Postgres to serve apps Databricks bought Neon in May 2025 and now headlines Lakebase in funding releases. The lakehouse needed a real database, and that says where apps are going. Read