Use managed PostgreSQL in Databricks Apps
By Steven Van ·
Publishing a Databricks App in Replit now provisions Lakebase automatically and applies schema changes; other templates keep using Replit's own database.
Replit's Databricks App template now uses Lakebase, Databricks' managed production PostgreSQL, as the app's backing database. Developers build and test against a separate development database inside Replit, and when the app is published, Replit provisions the Lakebase database in the Databricks workspace and applies the project's schema changes automatically.
Lakebase is meant for application state, such as user accounts, settings and transactions, while a SQL Warehouse still handles analytics and Unity Catalog data. Databricks Apps published with other templates continue to use a standard Replit production database instead of Lakebase.
