Show Notes
Eventstreams look healthy on the canvas while silently dropping events. We pull apart the no-code abstraction, trace three silent failure modes, and reckon with the four billing meters that confuse every FinOps team.
More from Microsoft Fabric Architecture Podcast
Medallion is the recommended design approach for Fabric. It's also one building block out of five, and the one that sends you a maintenance invoice nobody put on the architecture diagram. What the file-count guardrail means for Direct Lake on OneLake, why schema-enabled lakehouses can't use the automated maintenance activity, and when the whole pattern is overkill.
Databricks and Fabric have five integration paths, not one. Each moves data. None moves permissions. We pull apart the one-credential model, the hour-long revoke delay, and the ADLS shortcut that silently bypasses Unity Catalog's row-level security.
Fabric doesn't charge you when work happens — it spreads the cost forward into 2,880 thirty-second timepoints. That one sentence explains every confusing capacity behavior, including why surge protection can reject the SQL it's supposed to protect.
Fabric domains look like governance boundaries but the documentation says otherwise. We unpack what a domain actually gives you, the default-domain mechanism that's still running in your tenant, and why the label on the cabinet is not the lock.
Cosmos DB has no schema. Delta tables need one. When mirroring bridges the two, the replicator guesses — and the guess only ever widens. We trace where the bytes come from, why renamed properties leave ghost columns full of nulls, and what stop replication actually does.