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.

Featured
Lakeflow Connect Free Tier: $35/Day Back in Your Budget
Lakeflow Connect Free Tier: $35/Day Back in Your Budget
The Lakehouse Finally Has Real Transactions
The Lakehouse Finally Has Real Transactions
Why Your Databricks Upgrade Is Incomplete If You're Still Running ADF
Why Your Databricks Upgrade Is Incomplete If You're Still Running ADF

Explore More Content

Costs

EDW

ML & AI

AWS

Fabric

Databricks

Integrations

Migrations

Snowflake

Hadoop

Migrations Hubert Dudek Migrations Hubert Dudek

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.

Read More