Skip to content
All topics

Lakebase

Recent items mentioning Lakebase across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.

60 recent items1 release16 news19 videos24 community threads

What is Lakebase?

Lakebase Postgres is a fully managed Postgres database built into the Databricks platform. It's real Postgres, so standard drivers and clients work, and instead of a fixed server you provision a project with branches and databases inside it.

Analytics tables in the lakehouse are a poor fit for application backends that need low latency reads and writes, and that's the gap Lakebase fills without leaving the platform. You can sync Unity Catalog tables into Lakebase so applications query them quickly, and store Postgres changes back as Delta tables for pipelines and audit (that direction is in Public Preview). Autoscaling, scale-to-zero, and instant branching keep development and test environments cheap to create.

Lakebase reached general availability on January 22, 2026, with automated backups and point-in-time recovery; read replicas and high availability with automatic failover are also available, the latter added in March 2026. As of September 2026 it tracks current Postgres releases, with major versions 16, 17, and 18 supported.

Is Lakebase generally available?

Yes. Lakebase reached GA on January 22, 2026, including autoscaling, scale-to-zero, instant branching, automated backups, and point-in-time recovery. One notable exception is storing Postgres changes as Delta tables with full change history, which is in Public Preview.

Is Lakebase real Postgres or just Postgres compatible?

It's actual managed Postgres, and standard Postgres drivers and clients work against it. As of September 2026 it supports Postgres major versions 16, 17, and 18.

How much does Lakebase cost?

Billing is usage based and began in January 2026, with snapshot storage billed separately since June 1, 2026. Scale-to-zero and autoscaling are the main levers for keeping idle branches and quiet databases cheap; Databricks publishes current rates per cloud and region on its pricing page.

Do I need Lakebase if I already have the lakehouse?

The lakehouse handles analytics, while Lakebase is for transactional application workloads that need low latency reads and writes. The two connect: you can sync Unity Catalog tables into Lakebase for fast serving, and capture Postgres changes back as Delta tables for downstream pipelines and audit.

Sources: Lakebase Postgres (Databricks docs) · Lakebase release notes (Databricks docs)

What's happening in LakebaseAI synthesis · updated Nov 19, 2026

Built directly on Delta and Iceberg storage rather than external replication pipelines 9, Lakebase Postgres delivers an LTAP architecture that serves 99.46% of reads without leaving the compute node 4. Databricks also launched Lakebase Insights, an autonomous telemetry agent that flags deadlocks and missing indexes for Genie-assisted remediation 56, while teams increasingly leverage copy-on-write database branching to safely evaluate AI agents against production data 310.

Generated daily from the 10 most recent items mentioning Lakebase. Click any [N] to jump to the source.

Databricks CommunityData Engineering

Predictive Optimization keeps running on system.lakebase after disabling it at account level

00today
Databricks CommunityLakebase Articles

Transactional apps on Databricks: Lakebase owns the decision, Delta gets the copy

004d ago
Databricks CommunityLakebase Discussions

Lakebase in production: what surprised you?

006d ago
Databricks CommunityData Engineering

Lakebase Data API

001w ago
Databricks CommunityLakebase Articles

Announcement | Lakebase branching for CI/CD: lessons from 100 PR databases

001w ago
Reddit

DQX Studio - Data Quality App

Saw this app available on the marketplace: https://marketplace.databricks.com/details/99214a23-5dc6-48c4-968d-c1f0a6ed8c37/Databricks\_DQX-Studio-Data-Quality-App Do Databricks Apps like the above have any dependencies e.g. Lakebase that I need to pre provision? Or is that all taken care of after hitting the "get access" button? Also, are all these apps free? Is the DQX app free? submitted by /u/RazzmatazzLiving1323 [link] [comments]

00RazzmatazzLiving13231w ago
Databricks CommunityData Engineering

Zerobus to lakebase

001w ago
Reddit

Lakebase streaming sync is now GA

Hey Reddit, I’m happy to share one more new feature. The Lakebase streaming sync is now officially GA. Lots of customers are already using this feature to write streaming data with latency in 10s of milliseconds to Lakebase. It's much simpler to use than foreachBatch and you don't have to worry about connection pools, rate limits, error handling, etc. Here's what's new since we announced the Public Preview earlier this year: Declarative merge strategies*: Choose, per column, how an incoming row is reconciled with the existing row on a primary-key conflict. For example, you can keep the latest non-null value, keep the first value written, or take the value from the row with the latest event time. No custom SQL is required. External PostgreSQL via UC connections (Public Preview)*: Write to Postgres databases outside Lakebase, authenticated through a Unity Catalog connection so no credentials live in code. INTERVAL types*: DayTimeInterval and YearMonthInterval columns map to Postgres interval on DBR 19 and above. Serverless support: The sink now runs on serverless compute for notebooks and jobs, using the AvailableNow trigger. \ Merge strategies, external Postgres, and interval types require DBR 19.* Example: df.writeStream .format("postgresql") .outputMode("update") // optional; can be append mode as well .option("upsertkey", "primaryKey") // optional .option("upsert.columnStrategies", "last_updated_at:greatest,status:latestBy(last_updated_at)") .toTable("catalog.schema.table") SDP support remains in Private Preview. Public Preview, which adds support for native Lakebase streaming tables, is slated for later this year. submitted by /u/inkypinky [link] [comments]

00inkypinky1w ago
Databricks CommunityDatabricks TV

Building on Lakebase | Episode 3: Branch, Test, and Ship: Release Changes Safely using Branching

002w ago
Reddit

Databricks Apps vs AKS + Lakebase for Business Applications

We’re currently evaluating two architecture options for an enterprise business application: Azure AKS/K8S + Databricks Lakebase: Host the application on AKS and use Lakebase as the transactional database. Databricks Apps + Lakebase: Host both the application and database within the Databricks ecosystem. The application itself is less analytics-focused and more geared toward supporting business operations, including workflows, CRUD operations, user management, RBAC, APIs, and integrations with other systems. I’m leaning toward AKS given its flexibility and maturity, but Databricks Apps seems appealing from an infrastructure management and deployment perspective. Curious if anyone has experience running business applications on Databricks Apps in production. A few things I’m particularly interested in: - Any limitations with scalability, performance, or concurrent users? - How does Databricks Apps handle complex backend logic and external integrations? - Any challenges with CI/CD, monitoring, authentication, or environment management? - How do the costs compare once you factor in infrastructure and operational overhead? - Is Databricks Apps mature enough for business-critical applications, or is AKS still the safer choice? Would appreciate any real-world experience or lessons learned, especially from those who have worked with both approaches. submitted by /u/Conscious_Awareness6 [link] [comments]

00Conscious_Awareness62w ago
Databricks CommunityCommunity Articles

Lakebase Change Data Feed exports whole schemas: feed it one event table instead

002w ago
Databricks CommunityLakebase Discussions

Lakebase synced tables: how can a database owner/admin configure default SELECT privileges for the m

002w ago
Databricks CommunityGet Started Discussions

Built my AngelHack Quest 4 App with Databricks Apps + Lakebase

002w ago
Databricks CommunityTechnical Blog

Serving the Lakebase Data API Through Azure API Management

002w ago
Reddit

Migrating Europe from RDS Postgres to Lakebase

submitted by /u/Limp-Park7849 [link] [comments]

00Limp-Park78492w ago
Reddit

How to add a resource to an app space?

Hi, I was testing out the Genie App Builder today and wanted to created an app which connects to a Lakebase postgres table. However, Genie told me the resource postgres is missing in the app (space) and I should add it. In the app settings I can't add the resource because the app is managed/restricted by the app space. But in the app space I cannot find the option to add the postgres resource either (according to the documentation only "User authorization", "Serverless usage policy", and "Permissions" can be configured https://learn.microsoft.com/en-us/azure/databricks/dev-tools/databricks-apps/app-spaces#configure ). Is it possible to add resources to app spaces? Or am I limited with them? submitted by /u/IIDraxII [link] [comments]

00IIDraxII3w ago
Databricks CommunityLakebase Articles

Test on a Branch, Not on Patients: Agentic Drug Substitution with Lakebase

003w ago
Reddit

AI Agent Memory

Databricks supports agent memory storage. The amazing part is that Lakebase stores the memory, so we can also inspect the saved record. We can save "User prefers Mexican recipes" and recall it through a client with the question "What should I cook for dinner?" more news https://medium.com/databrickscommunity/databricks-news-genie-cli-app-builder-agent-memory-dabs-41820427fcc2 submitted by /u/hubert-dudek [link] [comments]

00hubert-dudek3w ago
Databricks CommunityGet Started Discussions

Quest 4 Completed – Building and Deploying My First Databricks App with Lakebase

003w ago
Reddit

Databricks Apps/Jobs Deployment Issue on New Workspace: Due to Quota?

My company sells a data analytics application to professional sports teams. The application is built as a Databricks App, deployed into a customer's workspace. The underlying data model is seeded by ETL that lives in my own company's workspace, with the gold tables shared as pinned version views into the customer's workspace, where a daily job syncs the views into Lakebase on the customer side. I built this on Databricks partially because the customers typically don't have robust IT teams in-house. Rather than requiring them to self-manage a bunch of infrastructure or host my own costly SaaS backend, I figured I could save a lot of complexity by setting up a Databricks workspace for them and deploying the application code into it via DAB from a central repo. I'm having an issue with a new customer that I onboarded yesterday. They created a new Azure subscription for the purpose of deploying the Databricks workspace + our application. Everything deployed successfully, but the Databricks App stops itself after approximately two hours. At first I thought it was a transient issue and restarted the app, but it keeps recurring. Troubleshooting has been challenging, because App logs are not visible when an App is stopped. I was able to get the following from the CLI ( databricks apps get -o json ): "app_status": { "message": "App status is unavailable.", "state": "UNAVAILABLE" }, "compute_size": "MEDIUM", "compute_status": { "message": "App compute was stopped due to workspace or account status.", "state": "STOPPED" }, Both the Azure subscription (Azure Plan) and the Databricks workspace (Premium + RBAC) do not appear to be in a trial state. Both were set up in the past 48 hours. I suspect this is some kind of new workspace restriction on the Databricks side, but I'm not sure what can be done about it. The App is deployed into a few different workspaces and runs without issue, but all of the workspaces have existed for a while. This is the first Workspace that was deployed specifically for the App. I found this thread on Databricks Community that describes a similar issue, but it appears to have died without a resolution. Has anyone run into a similar issue, and is there anything that can be done about this? It's likely that many of our customers will need a new Databricks workspace to deploy our application, so if this is a recurring issue, we may need to rethink our entire architecture. submitted by /u/Minute_Visual_3423 [link] [comments]

00Minute_Visual_34233w ago
Reddit

LTAP without lakebase?

Is there any world where an LTAP architecture can be created that does NOT include lakebase, or databricks for that matter? It seems to me that it isn't much more than a marketing term for selling lakebase. Every public doc about LTAP has references to lakebase sprinkled all over it. Lakebase is mentioned from the beginning to the very end. As I understand LTAP is essentially defined as a shared storage layer for OLTP and analytics workloads. And that sort of storage is an implementation detail that is ONLY found in the deepest and most proprietary parts of lakebase. (IMO, Microsoft has had their own flavor of LTAP for many years, in the form of Fabric DW. That engine looks and acts similar to a TSQL database, yet emits lakehouse files in storage. Yet I suppose it lacks some very particular features, or performs badly on certain disqualifying OLTP workloads. The disqualifications will always allow a databricks salesman to refuse to call it LTAP. If these disqualifications aren't purely subjective, then maybe we also need to define LTAP in terms of a certain TPS threshold and a certain set of minimal DBMS capabilities. I haven't seen anything like that.) submitted by /u/SmallAd3697 [link] [comments]

00SmallAd36974w ago
Reddit

Performance Test - Batch-Loaded Unique Constraint Validation in Lakebase

The vendors that create big-data engines keep saying it is so challenging and costly to enforce uniqueness constraints in their managed catalogs (eg. in technologies like UC managed tables, that live on top of lakehouse blobs). They say it "doesn't scale". And that it gets more challenging at large volumes. But this is like anything else - customers should still be empowered to use features that may not always scale well. Would this problem get easier if they offered it only for certain data types like 32 bit unsigned integers? Lets consider Lakebase. Lets say I'm a user of Lakebase, and I'm running sequential batch transactions to insert a consecutive series of 1000 integers at a time that are validated by the database to be unique. How long would it take until those transactions to become slower than 100ms? Should I expect to to insert all 4 billion integers and never see any transaction take longer than 100ms? Now lets do a similar thing in a UC managed table , where we insert the same sequentially increasing 1000 integers at a time, and I check for the uniqueness of these myself in my serializable insert transactions. (Because the UC managed table won't help me with that.) Obviously my uniqueness validations would start to slow down over time. As I approach the limit of 4 billion integers I would expect the insert operations to take longer than lakebase , but possibly never more than one second per transaction. Does that sound about right? (If necessary I might use cheats, like break apart the integer into four columns of one byte each, then use partitioning). TLDR, validating uniqueness with 32 bit integers may be harder in a UC managed-table than for lakebase. But IMO that does NOT mean customers should be doing the heavy lifting ourselves. These lakehouse-based technologies should give us a mechanism for it, even if there are restrictions (ie. certain data types, tables of no more than 4 billion rows, etc). submitted by /u/SmallAd3697 [link] [comments]

00SmallAd36974w ago
Databricks CommunityDatabricks TV

Lakebase: Postgres That Actually Likes Your Lakehouse

004w ago
Databricks CommunityDatabricks TV

How to Sync Lakebase Tables to Delta with Lakehouse Sync

001mo ago

Get Tuesday's version of this

Tracking Lakebase? The Tuesday email carries what moved across the whole ecosystem, not just this topic. Free, one-click unsubscribe.

Read past issues first