Hi everyone,
Databricks has shipped a lot of new features recently. Hereโs a quick summary of the most useful ones, grouped by area.
1. DABs Deployment History
What it is:
Databricks Asset Bundles (DABs) now keep a history of every deployment. Each record shows the deployment version, its status, and the resources it manages.
Why it matters:
Until now, working out what changed between two bundle deployments meant digging through Git history or comparing configurations by hand. Deployment history shows those changes directly. For example, if you raise a jobโs timeout from 60 to 120 seconds and redeploy, the history records exactly that change.
Where youโd use it:
- Auditing changes in production environments
- Troubleshooting when a job starts behaving differently after a deployment
- Getting better visibility in CI/CD pipelines built on DABs
2. Genie Code CLI
What it is:
Genie Code, the Databricks AI coding assistant, now runs from your terminal. It works with your local files and Databricks workflows.
Why it matters:
Many developers spend most of their time in a local IDE and terminal. With the CLI, you get AI help without switching to the workspace UI. You can ask it to compare two bundle files, upload files, or help with workflow-related tasks.
Good to know:
Model usage from the CLI is billed through Unity Gateway, so cost tracking and governance stay in one place.
Where youโd use it:
- Reviewing changes between bundle configurations
- Doing routine file and workflow tasks faster
- Local-first development
3. Genie App Builder
What it is:
Describe the app you want in plain language, and Genie App Builder creates a Databricks App. You can then keep refining it through chat.
Why it matters:
Building even a simple internal app used to take frontend skills and setup time. Now you can go from an idea to a working prototype in minutes. The original articleโs example is a news tracker with sample data that filters six cards by topic, built from a short description.
Governance:
Building, sharing and permissions are controlled through App Spaces, so teams can create apps quickly without losing control over who builds and who can access them.
Where youโd use it:
- Quick internal tools and dashboards
- Prototypes to show business stakeholders
- Letting analysts and less technical users build simple apps
4. Materialized Views and Streaming Tables from Python
What it is:
You can now create standalone materialized views and streaming tables directly from a serverless notebook, using the @DP.materialized_view and @DP.table decorators.
Why it matters:
Previously these objects were usually defined inside a full declarative pipeline. Now, for simpler cases, you can define them right in a notebook in Python, which means less setup and faster development.
Where youโd use it:
- Quick incremental aggregations
- Lightweight streaming ingestion
- Testing transformation logic before moving it into a full pipeline
5. JDBC Connections in Unity Catalog (Generally Available)
What it is:
You can save a JDBC driver, endpoint and credentials once as a Unity Catalog connection, then use it by name in any notebook.
Requirements:
Serverless compute and DBR 19 or above.
Why it matters:
Teams often copy connection strings and credentials across many notebooks, which is a maintenance headache and a security risk. With UC JDBC connections:
- Credentials are stored once and governed centrally
- Access is controlled through Unity Catalog permissions
- Notebooks stay clean, with no hardcoded connection details
Where youโd use it:
- Reading from external databases such as MySQL, PostgreSQL or SQL Server
- Sharing approved connections across teams safely
6. Audio Transcription in SQL with ai_transcribe (Beta)
What it is:
A new AI function that turns audio into timestamped text with speaker labels, called directly from SQL.
Languages: English and Spanish (currently)
Why it matters:
Audio data used to need separate speech-to-text services and custom pipelines. Now you can transcribe audio with a simple SQL query, then analyze the text with other AI functions such as ai_summarize, ai_classify or ai_analyze_sentiment, all within Databricks.
Where youโd use it:
- Call-center analytics (customer sentiment, complaint detection)
- Meeting and interview transcription
- Compliance monitoring of recorded calls
7. Agent Memory
What it is:
AI agents can now store useful facts and user preferences and use them in later conversations. The memory is stored in Lakebase.
Why it matters:
Without memory, every conversation with an agent starts from scratch. With Agent Memory, the agent remembers context. In the original articleโs example, a userโs preferred news format is saved and used in a later session, without the earlier conversation being sent again.
Where youโd use it:
- Personalized assistants and chatbots
- Customer support agents that remember past interactions
- Internal copilots that learn team preferences over time
