Loading…
Topic
Databricks Apps
1 post about Databricks Apps. Every summary links to the original.
- 1 post
- 1 company
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
A builder’s guide to scaling Databricks Apps
As a Databricks Apps application scales from a few users to thousands across an organization, it must handle growing demand without latency spikes or outages. The guide proposes a four-stage approach: set targets during design, build with async code and recoverable state, test with load simulations, and operate with monitoring. Keep app compute focused on serving the UI; send heavy work to Lakebase, Databricks Jobs, or Sandbox, and choose a framework like AppKit that offers built-in caching and telemetry. Separate session state into soft state (rebuildable from hard state) and hard state stored durably in Lakebase or Unity Catalog so any instance can reconstruct a session after restarts or scaling. Use load tests to validate concurrency and bursts, then consult system metrics on CPU, memory, timeouts, and connections to decide whether to scale up to a larger instance or scale out with more instances.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.