Databricks publishes four-stage guide to scaling Databricks Apps
Overview
Databricks publishes a guide to scaling Databricks Apps in four stages: design, build, test and deploy, and operate.
The guide recommends setting latency and peak-load targets first, keeping session state rebuildable, and using load tests to choose instance size and count.
The guide estimates Lakebase database connections as instances × workers × pool size. It states that the default limit is five instances per app, and that a Databricks representative can raise the limit if load testing shows more is needed. It also says each user who queries Lakebase as themselves needs their own Postgres role, and that Lakebase allows 500 roles per branch.
Written by AI from the articles below · updated Nov 5, 2:10 PM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
- Databricks BlogOfficialDatabricks explains how to scale Databricks Apps across four stages
AIDatabricks publishes a four-stage guide to scaling Databricks Apps: design, build, test and deploy, and operate. It recommends setting latency and peak-load targets first, keeping session state rebuildable, and using load tests to choose instance size and count. The guide also estimates Lakebase connections as instances × workers × pool size, and notes the default limit is five instances per app.
Heat Trend
Not enough continuous observations to show a trend yet.