databricks-lakebase-provisioned

To provision Databricks Lakebase PostgreSQL for OLTP workloads, you create a managed instance by specifying a name and capacity size, such as CU_1. This provisions a managed PostgreSQL database for transactional application state.

You generate short-lived OAuth tokens for Lakebase PostgreSQL connections that expire every 1 hour. Connections require SSL and must use these tokens for secure authentication instead of static passwords.

Yes, Lakebase Provisioned supports reverse ETL by syncing Delta tables to PostgreSQL. This enables OLTP access patterns using synced tables with appropriate scheduling policies for data movement.

Yes, you can wire Lakebase Provisioned instances into Unity Catalog for governance. This registers the managed PostgreSQL resources within your existing Databricks data governance framework.

For long-running apps connected to Lakebase, you must implement token refresh logic to handle the 1-hour OAuth token expiry. This ensures continuous connectivity without authentication interruptions.

Use managed Lakebase PostgreSQL when you need persistent state for Databricks Apps, agent memory, or reverse ETL without building bespoke infrastructure or brittle authentication flows for your transactional workloads.