Microsoft Fabric
Lakehouse topology, Direct Lake, refresh, CI/CD blast radius, and Fabric platform contracts.
Fabric Airflow: Is It Possible to Use Apache Airflow with Fabric?
Keep Fabric as the execution plane and Airflow as the orchestration plane. Thin tasks, terminal-state success, and the failure modes that show up when you collapse both into one tool.
Lakehouse Design: One Lakehouse with Schemas, or Many Lakehouses?
How to choose between multiple Fabric lakehouses and a schema-enabled lakehouse for bronze, silver, and gold, including CI/CD and naming fallout.
Direct Lake: Do You Still Need to Refresh a Semantic Model?
How to choose notebook, pipeline, or scheduled refresh for lakehouse semantics, and when Direct Lake beats a SQL endpoint for heavy facts.
Semantic Migration: How Do You Rebind Reports When the Model Moves to Lakehouse?
Why lakehouse migrations fail on NULL versus zero, float drift, and type rebase settings, and how to treat parity as a contract.
Fabric CI/CD: How Do You Limit Blast Radius Across Dev Workspaces?
Why Fabric deployment tooling can republish unchanged notebooks and how to design for stable identities and smaller blast radius.
OneLake Shortcuts: Should Shortcuts Stay Bronze-Only?
Argue that bronze should be a contract of OneLake shortcuts and clean views, not a second physical copy of upstream gold and silver.
Gold + Direct Lake: Direct Lake or Import for Large Fact Tables?
Show why a high-volume source table belongs in gold as a documented fact table with shared key matching and Direct Lake storage mode for volume.
Gold Semantic Contract: Can You Choose Which Columns Reach the Direct Lake Model?
Argue that gold tables only become platform assets when unmatched keys, captions, and relationships are explicit in the semantic model.
Workspace Naming: Is a One-Time Rename Cheaper Than Translating Prefixes Forever?
Argue that inconsistent workspace display-name prefixes create operational tax and that a one-time rename with stable catalog names is cheaper than perpetual translation layers.
Fabric CI/CD: Merge the whole ladder, or cherry-pick what is ready?
In a multi-dev Fabric test to staging to main ladder, merge the tip only when everything is ready. Safer selective promotion cherry-picks squash commits onto a temp branch, opens a PR, then deploys.