Margin notes · Databricks
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.
6 notes
Nothing matched that. Try a broader term, or clear the filter.
- Databricks will keep your agent's memory, in Postgres Managed agent memory and sessions are in beta, both backed by Lakebase and usable from any framework. The state layer teams were building by hand. Read
- You can now share data you never loaded into Databricks OpenSharing now shares foreign Iceberg tables and foreign schemas federated from other systems, and the provider pays the compute cost Read
- LTAP Direct Writes is the first piece of the one-copy claim you can measure LTAP Direct Writes, in beta since 25 August 2026, loads synced tables by writing to storage instead of through compute. The first LTAP claim a team can time. Read
- Lakebase is compliant everywhere now, and the last excuse went with it Lakebase carries PCI-DSS and HITRUST in every AWS region since 8 September 2026, is on by default in compliance workspaces, and its APIs are GA. Read
- The growth is your invoice Databricks run-rate grew over 80% while customers grew a third. The gap is existing customers spending more. If you are one of them, that growth is your bill. Read
- Databricks bought a Postgres because the lakehouse couldn't serve an app 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