Skip to content
All topics

Databricks Apps

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

33 recent items3 releases4 news23 videos3 community threads
What's happening in Databricks AppsAI synthesis · updated 10d ago

Developers can now construct and deploy Databricks Apps directly by feeding copyable Developer Hub prompts into AI coding assistants like Cursor 9 or Replit 10. In production, pairing Databricks Apps with Lakebase Postgres and route-optimized Model Serving yields p50 latencies of 27 ms under 5,000 requests for real-time fraud scoring 8, enabling enterprise deployments like NorthStar Anesthesia's clinician scheduling tool built for 3,000 workers 4.

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

Databricks CommunityData Engineering

Databricks Apps - "App Not Available" error with locationId parameter missing

002w ago
Databricks CommunityData Engineering

Databricks Apps (Streamlit) - How to Implement Proper Logout Functionality?

003w ago
Stack Overflow

Databricks Marketplace: IP Protection, Job Compute, and Secret Management

I am planning to publish an application through Databricks Marketplace. The application contains proprietary business logic and processing algorithms that must not be accessible to customers after installation. Customers should be able to use the application to process data in their own Databricks environment, but they should not be able to inspect, copy, or reuse the underlying implementation. Approaches I Have Tried I have considered the following approaches: Packaging the implementation as Python wheels or other artifacts. Hosting the implementation as private Python packages. Deploying the application source from a private Git repository. With the packaging approach, the underlying Python implementation may still be accessible or inspectable from notebooks, workspace files, cluster environments, package caches, or other customer-accessible locations. This does not meet my IP-protection requirements. With private package hosting, the package installation requires an access token or API key. Providing a reusable package-registry credential to an application running in the customer's workspace creates a risk that the credential could be extracted or reused to download the private package outside the intended application flow. I also understand that Databricks Marketplace reviewers may require the submitted application code to be human-readable during the review process. Therefore, I am looking for an architecture that protects the production implementation without relying only on code obfuscation. Current Understanding My understanding is that a Databricks App runs in an isolated, containerized runtime. This provides separation between the application runtime and normal customer workspace resources. However, my workload includes processing large datasets. I understand that Databricks App compute is primarily intended to run the application, API, or user interface, rather than perform large-scale Spark processing. Because of this, I am unsure whether Databricks App […truncated]

advicedatabricksdatabricks-unity-catalog
-70No One3w ago