Resources and insights
Our Blog
Explore insights and practical tips on mastering Databricks Data Intelligence Platform and the full spectrum of today's modern data ecosystem.
Most teams that move to Databricks get the hard part right. They migrate the processing engine, rebuild the transformation logic, and stand up Unity Catalog. Then they leave Azure Data Factory running in the background: connected to everything, owned by nobody, and quietly accumulating cost and complexity. In this entry, that’s the gap we address.
Explore More Content
ML & AI
Lakeflow Connect Free Tier: $35/Day Back in Your Budget
Databricks' permanent Lakeflow Connect free tier delivers 100 DBUs per workspace per day — covering up to 100 million records of ingestion at no additional compute cost. For enterprise teams running multiple workspaces, that's over $255,000 in avoided annual costs. This post breaks down the economics, architecture, and what it means for teams still paying a third-party ETL tax.
Why Your Databricks Upgrade Is Incomplete If You're Still Running ADF
Still running ADF after moving to Databricks? Here's why it happens, what it's costing your governance story, and how Lakeflow Jobs closes the gap.
Your Databricks Stack Is Modern. Your Orchestration Isn't.
Most Databricks migrations modernize the processing engine and leave Azure Data Factory running untouched. This post explains why that gap is a compounding business risk, and maps out the three practical paths to migrating orchestration to Lakeflow Jobs, including the on-prem push pattern that removes the most common blocker.
The Nightmare of Initial Load (And How to Tame It)
Initial data loads don't have to be nightmares. Discover the split Bronze table pattern that separates historical backfills from incremental streaming.
Data Intelligence for All: 9 Ways Databricks Just Redefined the Future of Data
Discover how Databricks' 9 major announcements at Summit 2025 are democratizing AI with Agent Bricks, Lakebase, free edition, and more game-changing innovations.