Microsoft Fabric Architecture Podcast Transistor (https://transistor.fm) https://feeds.transistor.fm/fabric-architecture-podcast Architecture decisions for Microsoft Fabric. Anonymized real customer scenarios, cost realism, counter-arguments included. Weekly episodes aligned with Fabric Friday recordings. © 2026 Matthias Falland 4a3b41f3-09cf-5c55-b990-9c25a1a38196 yes Welcome to the Fabric Architecture Podcast en Fri, 04 Sep 2026 10:00:08 +0200 Fri, 04 Sep 2026 10:02:09 +0200 https://www.fabricperiodictable.com https://img.transistorcdn.com/7KCGajg_Tv2rIKYSAqycTQ0OleaRmSrQ8iAKWGsMnsE/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xNmZi/MmU3NmY4ODZmMGNi/MTQxNGU3YzdiYzI5/YzEzNS5wbmc.jpg Microsoft Fabric Architecture Podcast https://www.fabricperiodictable.com episodic Matthias Falland Architecture decisions for Microsoft Fabric. Anonymized real customer scenarios, cost realism, counter-arguments included. Weekly episodes aligned with Fabric Friday recordings. Architecture decisions for Microsoft Fabric. technology, ai, data, fabric, microsoft Matthias Falland matthias@falland.ch No No The Folder That Carries Four Boundaries — Fabric Workspaces 36 36 The Folder That Carries Four Boundaries — Fabric Workspaces full 142b480e-b6c1-4287-bec2-2139cea7bf94 https://share.transistor.fm/s/b1be2cc9 The Folder That Carries Four Boundaries

Episode 36 • 2026-09-04 Duration: 10:19

A Fabric workspace isn't a folder — it's a cut through OneLake carrying every access rule, capacity bill, and residency commitment. Fabia and Matthias trace the boundaries hiding inside one object, starting with the documented fact that Contributor overrides OneLake security and ending with why a cross-region move is a deletion disguised as a dropdown.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Somewhere in your tenant right now, a workspace someone created in thirty seconds is quietly running up a bill in a region nobody chose.
  • Four boundaries. Creating a workspace means deciding who reads the data, what capacity it burns, which region holds it, and how it moves through your release cycle. The one people hear is the first. The other three sit there, quietly...
  • If your team needs to build inside the workspace, Contributor is the minimum role that lets them do the work.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> The Folder That Carries Four Boundaries

Episode 36 • 2026-09-04 Duration: 10:19

A Fabric workspace isn't a folder — it's a cut through OneLake carrying every access rule, capacity bill, and residency commitment. Fabia and Matthias trace the boundaries hiding inside one object, starting with the documented fact that Contributor overrides OneLake security and ending with why a cross-region move is a deletion disguised as a dropdown.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Somewhere in your tenant right now, a workspace someone created in thirty seconds is quietly running up a bill in a region nobody chose.
  • Four boundaries. Creating a workspace means deciding who reads the data, what capacity it burns, which region holds it, and how it moves through your release cycle. The one people hear is the first. The other three sit there, quietly...
  • If your team needs to build inside the workspace, Contributor is the minimum role that lets them do the work.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> Fri, 04 Sep 2026 10:00:00 +0200 Matthias Falland Matthias Falland 620 A Fabric workspace isn't a folder — it's a cut through OneLake carrying every access rule, capacity bill, and residency commitment. Fabia and Matthias trace the boundaries hiding inside one object, starting with the documented fact that Contributor overrides OneLake security and ending with why a cross-region move is a deletion disguised as a dropdown. A Fabric workspace isn't a folder — it's a cut through OneLake carrying every access rule, capacity bill, and residency commitment. Fabia and Matthias trace the boundaries hiding inside one object, starting with the documented fact that Contributor overri microsoft-fabric,data-architecture,podcast No When Your Graph Query Lies to You — Fabric Graph 35 35 When Your Graph Query Lies to You — Fabric Graph full 7a2e29ff-5a6f-4283-ba12-fd2db6345f5f https://share.transistor.fm/s/8e63c02b When Your Graph Query Lies to You

Episode 35 • 2026-08-28 Duration: 9:41

Graph in Fabric materialises a snapshot of your data's relationships the moment you save the model. That one decision explains the stale queryset, the failed-to-load error and the corruption right after a save. The 64 MB truncation is a separate limit, and it is the one nobody warns you about.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • Risks of the recommended path
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The pattern we keep seeing in the field
  • The architectural principle to take home

Key takeaways

  • A graph in Fabric is a photograph of your data's relationships.
  • Three products, zero overlap. Good luck with that steering committee.
  • Show me the query pattern. If the question is about paths between entities, and the audience is the team that owns the data, graph gives you something SQL genuinely cannot express. If the audience needs to leave the workspace, or if a join...

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> When Your Graph Query Lies to You

Episode 35 • 2026-08-28 Duration: 9:41

Graph in Fabric materialises a snapshot of your data's relationships the moment you save the model. That one decision explains the stale queryset, the failed-to-load error and the corruption right after a save. The 64 MB truncation is a separate limit, and it is the one nobody warns you about.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • Risks of the recommended path
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The pattern we keep seeing in the field
  • The architectural principle to take home

Key takeaways

  • A graph in Fabric is a photograph of your data's relationships.
  • Three products, zero overlap. Good luck with that steering committee.
  • Show me the query pattern. If the question is about paths between entities, and the audience is the team that owns the data, graph gives you something SQL genuinely cannot express. If the audience needs to leave the workspace, or if a join...

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> Fri, 28 Aug 2026 10:00:00 +0200 Matthias Falland Matthias Falland 582 Graph in Fabric materialises a snapshot of your data's relationships the moment you save the model. That one decision explains the stale queryset, the failed-to-load error and the corruption right after a save. The 64 MB truncation is a separate limit, and it is the one nobody warns you about. Graph in Fabric materialises a snapshot of your data's relationships the moment you save the model. That one decision explains the stale queryset, the failed-to-load error and the corruption right after a save. The 64 MB truncation is a separate limit, an microsoft-fabric,data-architecture,podcast No The Radio Button That Sets Your Security Architecture — API for GraphQL 34 34 The Radio Button That Sets Your Security Architecture — API for GraphQL full 1a729b41-508f-409d-a199-4c2d38ac33de https://share.transistor.fm/s/728ba25f The Radio Button That Sets Your Security Architecture

Episode 34 • 2026-08-21 Duration: 10:47

Fabric generates a GraphQL API from your warehouse in under a minute. But the connectivity dialog you see once decides your security posture, your RLS enforcement, and whether your production deployment silently reads development data. We trace the consequences.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Somewhere right now there's a GraphQL API returning clean JSON, passing every health check, serving an app that went live last quarter — and the table it's describing hasn't looked like that since May.
  • — which means the schema-drift problem we've been circling for ten minutes now applies to whatever your agents are reading too.
  • And look — saved credentials are genuinely the right answer in a real set of cases.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> The Radio Button That Sets Your Security Architecture

Episode 34 • 2026-08-21 Duration: 10:47

Fabric generates a GraphQL API from your warehouse in under a minute. But the connectivity dialog you see once decides your security posture, your RLS enforcement, and whether your production deployment silently reads development data. We trace the consequences.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Somewhere right now there's a GraphQL API returning clean JSON, passing every health check, serving an app that went live last quarter — and the table it's describing hasn't looked like that since May.
  • — which means the schema-drift problem we've been circling for ten minutes now applies to whatever your agents are reading too.
  • And look — saved credentials are genuinely the right answer in a real set of cases.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> Fri, 21 Aug 2026 10:00:00 +0200 Matthias Falland Matthias Falland 648 Fabric generates a GraphQL API from your warehouse in under a minute. But the connectivity dialog you see once decides your security posture, your RLS enforcement, and whether your production deployment silently reads development data. We trace the consequences. Fabric generates a GraphQL API from your warehouse in under a minute. But the connectivity dialog you see once decides your security posture, your RLS enforcement, and whether your production deployment silently reads development data. We trace the conseq microsoft-fabric,data-architecture,podcast No The Permission Broker That Outlives You — Org Apps in Fabric 33 33 The Permission Broker That Outlives You — Org Apps in Fabric full c80bcd4d-dad7-4ce8-ad2a-cfc2dd722748 https://share.transistor.fm/s/ca2cf3ae The Permission Broker That Outlives You

Episode 33 • 2026-08-14 Duration: 9:45

Org apps solved the decade-old broken-visual problem by managing permissions along the dependency chain. But the same engine that grants access on your behalf can leave records behind that you no longer have the rights to remove, and a single audience toggle can blow open an entire app.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The concrete recommended architecture
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, there's a semantic model with an access record that was created by an org app edit, by someone who no longer has the authority to undo it.
  • Pattern dictates platform. If your consumers need curated views of live workspace content, and you don't need dashboards, scorecards, or a publish gate — the org app is genuinely better at that job than workspace apps have ever been. The...
  • The thing I'd carry out of this episode is simpler than the feature list.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> The Permission Broker That Outlives You

Episode 33 • 2026-08-14 Duration: 9:45

Org apps solved the decade-old broken-visual problem by managing permissions along the dependency chain. But the same engine that grants access on your behalf can leave records behind that you no longer have the rights to remove, and a single audience toggle can blow open an entire app.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The concrete recommended architecture
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, there's a semantic model with an access record that was created by an org app edit, by someone who no longer has the authority to undo it.
  • Pattern dictates platform. If your consumers need curated views of live workspace content, and you don't need dashboards, scorecards, or a publish gate — the org app is genuinely better at that job than workspace apps have ever been. The...
  • The thing I'd carry out of this episode is simpler than the feature list.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> Fri, 14 Aug 2026 10:00:00 +0200 Matthias Falland Matthias Falland 586 Org apps solved the decade-old broken-visual problem by managing permissions along the dependency chain. But the same engine that grants access on your behalf can leave records behind that you no longer have the rights to remove, and a single audience toggle can blow open an entire app. Org apps solved the decade-old broken-visual problem by managing permissions along the dependency chain. But the same engine that grants access on your behalf can leave records behind that you no longer have the rights to remove, and a single audience tog microsoft-fabric,data-architecture,podcast No When Publish Succeeds and Nothing Changes — Power BI Apps 32 32 When Publish Succeeds and Nothing Changes — Power BI Apps full 8fc94057-41c6-4cc2-ba2a-7c436bb116af https://share.transistor.fm/s/86aeeb42 When Publish Succeeds and Nothing Changes

Episode 32 • 2026-08-07 Duration: 9:10

Power BI workspace apps promise a clean publish boundary between builders and consumers. But the mechanism that makes that boundary work — the copy, the separate IDs, the audience arithmetic — carries five traps that all fail in silence.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Pattern dictates platform. And this platform's pattern is silence. Somewhere right now, a team published their app, added three reports, and is waiting for users to call about them. The call's never coming. The reports are there,...
  • The thing I'd take from today is that this system was designed to succeed without confirming the outcome.
  • Which is exactly right for teams where speed matters more than ceremony.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> When Publish Succeeds and Nothing Changes

Episode 32 • 2026-08-07 Duration: 9:10

Power BI workspace apps promise a clean publish boundary between builders and consumers. But the mechanism that makes that boundary work — the copy, the separate IDs, the audience arithmetic — carries five traps that all fail in silence.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Pattern dictates platform. And this platform's pattern is silence. Somewhere right now, a team published their app, added three reports, and is waiting for users to call about them. The call's never coming. The reports are there,...
  • The thing I'd take from today is that this system was designed to succeed without confirming the outcome.
  • Which is exactly right for teams where speed matters more than ceremony.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.

Brand design based on fabricperiodictable.com.

]]> Fri, 07 Aug 2026 10:00:00 +0200 Matthias Falland Matthias Falland 551 Power BI workspace apps promise a clean publish boundary between builders and consumers. But the mechanism that makes that boundary work — the copy, the separate IDs, the audience arithmetic — carries five traps that all fail in silence. Power BI workspace apps promise a clean publish boundary between builders and consumers. But the mechanism that makes that boundary work — the copy, the separate IDs, the audience arithmetic — carries five traps that all fail in silence. microsoft-fabric,data-architecture,podcast No The Database Hiding Inside Your Scorecard — Fabric Scorecards 31 31 The Database Hiding Inside Your Scorecard — Fabric Scorecards full 24c019a0-b02a-4bbf-81bb-51be3620f49e https://share.transistor.fm/s/e586345b The Database Hiding Inside Your Scorecard

Episode 31 • 2026-07-31 Duration: 10:32

A scorecard silently creates its own semantic model the moment you hit New. That one architectural fact — that it's a stateful writer, not a read-only lens — explains why RLS doesn't carry over, why refresh breaks upstream, and why rollups leak across permission boundaries.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home
  • The concrete recommended architecture

Key takeaways

  • Somewhere right now, a scorecard with forty goals is showing all-green because nobody's checked in since March.
  • So the lesson from all of this — a scorecard's the right tool when you need to know who promised what, and what they said when it slipped.
  • That's the correct choice for more teams than you'd expect.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> The Database Hiding Inside Your Scorecard

Episode 31 • 2026-07-31 Duration: 10:32

A scorecard silently creates its own semantic model the moment you hit New. That one architectural fact — that it's a stateful writer, not a read-only lens — explains why RLS doesn't carry over, why refresh breaks upstream, and why rollups leak across permission boundaries.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home
  • The concrete recommended architecture

Key takeaways

  • Somewhere right now, a scorecard with forty goals is showing all-green because nobody's checked in since March.
  • So the lesson from all of this — a scorecard's the right tool when you need to know who promised what, and what they said when it slipped.
  • That's the correct choice for more teams than you'd expect.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 31 Jul 2026 10:00:00 +0200 Matthias Falland Matthias Falland 633 A scorecard silently creates its own semantic model the moment you hit New. That one architectural fact — that it's a stateful writer, not a read-only lens — explains why RLS doesn't carry over, why refresh breaks upstream, and why rollups leak across permission boundaries. A scorecard silently creates its own semantic model the moment you hit New. That one architectural fact — that it's a stateful writer, not a read-only lens — explains why RLS doesn't carry over, why refresh breaks upstream, and why rollups leak across per microsoft-fabric,data-architecture,podcast No One Expression Halves Your Data Ceiling — Paginated Reports 30 30 One Expression Halves Your Data Ceiling — Paginated Reports full e5a5976b-89db-4300-821f-be67a73d7253 https://share.transistor.fm/s/a857abd5 One Expression Halves Your Data Ceiling

Episode 30 • 2026-07-24 Duration: 10:13

Paginated reports carry no data model, and that one design decision explains every limit teams hit in production. This episode traces the consequences from silent data drops to a tenant-wide security door that only opens one way, and lands on the question that makes the tool choice for you.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • Where the obvious answer breaks
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • And a Diagnostics button nobody's pressed is sitting there, ready to explain why.
  • Somewhere right now, a Monday-morning subscription is carrying a Weekday expression nobody remembers, heading for a ceiling that used to be a slope and is now a cliff.
  • Show me the query pattern. If the aggregation's in the right place, the report scales. If it isn't, no capacity tier saves you. That's the decision that actually matters.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> One Expression Halves Your Data Ceiling

Episode 30 • 2026-07-24 Duration: 10:13

Paginated reports carry no data model, and that one design decision explains every limit teams hit in production. This episode traces the consequences from silent data drops to a tenant-wide security door that only opens one way, and lands on the question that makes the tool choice for you.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • Where the obvious answer breaks
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • And a Diagnostics button nobody's pressed is sitting there, ready to explain why.
  • Somewhere right now, a Monday-morning subscription is carrying a Weekday expression nobody remembers, heading for a ceiling that used to be a slope and is now a cliff.
  • Show me the query pattern. If the aggregation's in the right place, the report scales. If it isn't, no capacity tier saves you. That's the decision that actually matters.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 24 Jul 2026 10:00:00 +0200 Matthias Falland Matthias Falland 614 Paginated reports carry no data model, and that one design decision explains every limit teams hit in production. This episode traces the consequences from silent data drops to a tenant-wide security door that only opens one way, and lands on the question that makes the tool choice for you. Paginated reports carry no data model, and that one design decision explains every limit teams hit in production. This episode traces the consequences from silent data drops to a tenant-wide security door that only opens one way, and lands on the question microsoft-fabric,data-architecture,podcast No The Dashboard That Can't Filter — Power BI Dashboards 29 29 The Dashboard That Can't Filter — Power BI Dashboards full 93a3d0ff-96d4-4733-9195-400433185af6 https://share.transistor.fm/s/db9ed150 The Dashboard That Can't Filter

Episode 29 • 2026-07-17 Duration: 9:51

A Power BI dashboard can show tiles from six different semantic models. It cannot filter a single one of them. We explain why the architecture makes that tradeoff inevitable, and what it means for choosing between dashboards and reports.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • Where the obvious answer breaks
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The concrete recommended architecture
  • The architectural principle to take home

Key takeaways

  • Both problems solve the moment you understand what you pinned.
  • Somewhere right now, someone's pinning a tile and wondering where the slicer went.
  • Show me the query pattern. If the pattern is 'monitor five numbers from five models,' the dashboard's exactly right. If the pattern is 'explore, filter, drill,' you wanted a report from the start.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> The Dashboard That Can't Filter

Episode 29 • 2026-07-17 Duration: 9:51

A Power BI dashboard can show tiles from six different semantic models. It cannot filter a single one of them. We explain why the architecture makes that tradeoff inevitable, and what it means for choosing between dashboards and reports.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • Where the obvious answer breaks
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The concrete recommended architecture
  • The architectural principle to take home

Key takeaways

  • Both problems solve the moment you understand what you pinned.
  • Somewhere right now, someone's pinning a tile and wondering where the slicer went.
  • Show me the query pattern. If the pattern is 'monitor five numbers from five models,' the dashboard's exactly right. If the pattern is 'explore, filter, drill,' you wanted a report from the start.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 17 Jul 2026 10:00:00 +0200 Matthias Falland Matthias Falland 592 A Power BI dashboard can show tiles from six different semantic models. It cannot filter a single one of them. We explain why the architecture makes that tradeoff inevitable, and what it means for choosing between dashboards and reports. A Power BI dashboard can show tiles from six different semantic models. It cannot filter a single one of them. We explain why the architecture makes that tradeoff inevitable, and what it means for choosing between dashboards and reports. microsoft-fabric,data-architecture,podcast No The Bucket Nobody Reads — Power BI Reports 28 28 The Bucket Nobody Reads — Power BI Reports full 283f46a1-c03e-41dd-85cd-03899cf89efd https://share.transistor.fm/s/5240513b The Bucket Nobody Reads

Episode 28 • 2026-07-10 Duration: 10:31

Every visual on a report page fires a DAX query. When twenty visuals queue behind a parallelism cap, the bottleneck hides in Performance Analyzer's least-read column — and the escape hatch everyone reaches for can silently produce wrong numbers.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • The concrete recommended architecture
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, a report page is loading twenty visuals, queueing twelve of them behind a parallelism cap, and the person watching the spinner is about to open Performance Analyzer, see a DAX number, and start tuning the wrong thing.
  • Show me the query pattern. That's what this comes down to. A report is a query generator. Every visual is a query, every page load is a fan-out, and every performance problem lives in the gap between what the author designed and what the...
  • The piece I'd take away is that the report author and the model owner have to be in the same conversation.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> The Bucket Nobody Reads

Episode 28 • 2026-07-10 Duration: 10:31

Every visual on a report page fires a DAX query. When twenty visuals queue behind a parallelism cap, the bottleneck hides in Performance Analyzer's least-read column — and the escape hatch everyone reaches for can silently produce wrong numbers.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • The concrete recommended architecture
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, a report page is loading twenty visuals, queueing twelve of them behind a parallelism cap, and the person watching the spinner is about to open Performance Analyzer, see a DAX number, and start tuning the wrong thing.
  • Show me the query pattern. That's what this comes down to. A report is a query generator. Every visual is a query, every page load is a fan-out, and every performance problem lives in the gap between what the author designed and what the...
  • The piece I'd take away is that the report author and the model owner have to be in the same conversation.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 10 Jul 2026 10:00:00 +0200 Matthias Falland Matthias Falland 632 Every visual on a report page fires a DAX query. When twenty visuals queue behind a parallelism cap, the bottleneck hides in Performance Analyzer's least-read column — and the escape hatch everyone reaches for can silently produce wrong numbers. Every visual on a report page fires a DAX query. When twenty visuals queue behind a parallelism cap, the bottleneck hides in Performance Analyzer's least-read column — and the escape hatch everyone reaches for can silently produce wrong numbers. microsoft-fabric,data-architecture,podcast No When Direct Lake Goes Quiet — Power BI Semantic Models 27 27 When Direct Lake Goes Quiet — Power BI Semantic Models full 055b6c4c-8190-45fa-a22b-1c326e997f0c https://share.transistor.fm/s/500ce8c7 When Direct Lake Goes Quiet

Episode 27 • 2026-07-03 Duration: 9:40

Direct Lake promises no refresh and VertiPaq speed at lake scale. But its failure modes are silent — it degrades instead of breaking. We pull apart framing, transcoding, and the fallback tax nobody talks about.

What we discuss

  • How it actually works underneath the abstraction
  • A real Reddit/Microsoft Q&A question unpacked
  • Where the obvious answer breaks
  • The concrete recommended architecture
  • The pattern we keep seeing in the field
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, a semantic model is serving yesterday's numbers.
  • Run TABLETRAITS before you ship. One line of DAX. It tells you whether your model is actually in Direct Lake mode — or quietly serving something else.
  • So the lesson — Direct Lake moved where the discipline lives.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> When Direct Lake Goes Quiet

Episode 27 • 2026-07-03 Duration: 9:40

Direct Lake promises no refresh and VertiPaq speed at lake scale. But its failure modes are silent — it degrades instead of breaking. We pull apart framing, transcoding, and the fallback tax nobody talks about.

What we discuss

  • How it actually works underneath the abstraction
  • A real Reddit/Microsoft Q&A question unpacked
  • Where the obvious answer breaks
  • The concrete recommended architecture
  • The pattern we keep seeing in the field
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, a semantic model is serving yesterday's numbers.
  • Run TABLETRAITS before you ship. One line of DAX. It tells you whether your model is actually in Direct Lake mode — or quietly serving something else.
  • So the lesson — Direct Lake moved where the discipline lives.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 03 Jul 2026 10:00:00 +0200 Matthias Falland Matthias Falland 581 Direct Lake promises no refresh and VertiPaq speed at lake scale. But its failure modes are silent — it degrades instead of breaking. We pull apart framing, transcoding, and the fallback tax nobody talks about. Direct Lake promises no refresh and VertiPaq speed at lake scale. But its failure modes are silent — it degrades instead of breaking. We pull apart framing, transcoding, and the fallback tax nobody talks about. microsoft-fabric,data-architecture,podcast No The Column Named C1 — Fabric Data Agent 26 26 The Column Named C1 — Fabric Data Agent full a2c5dc97-b1cc-4e50-bbbe-5d55fba49012 https://share.transistor.fm/s/74df63dc The Column Named C1

Episode 26 • 2026-06-26 Duration: 9:21

A Fabric Data Agent generates queries from your column names, not your intentions. This episode pulls apart the grounding pipeline to show where accuracy lives and dies — and why the schema investment you skipped three years ago just became urgent.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere, a data architect who's been filing those tickets for five years just felt a wave of vindication.
  • There's something to that. We spent years telling teams to name their columns properly and nobody listened, because the SQL worked either way. Now there's an LLM reading those column names and getting the wrong answer, and suddenly the...
  • Show me the query pattern — then show me the auth pattern.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> The Column Named C1

Episode 26 • 2026-06-26 Duration: 9:21

A Fabric Data Agent generates queries from your column names, not your intentions. This episode pulls apart the grounding pipeline to show where accuracy lives and dies — and why the schema investment you skipped three years ago just became urgent.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere, a data architect who's been filing those tickets for five years just felt a wave of vindication.
  • There's something to that. We spent years telling teams to name their columns properly and nobody listened, because the SQL worked either way. Now there's an LLM reading those column names and getting the wrong answer, and suddenly the...
  • Show me the query pattern — then show me the auth pattern.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 26 Jun 2026 10:00:00 +0200 Matthias Falland Matthias Falland 562 A Fabric Data Agent generates queries from your column names, not your intentions. This episode pulls apart the grounding pipeline to show where accuracy lives and dies — and why the schema investment you skipped three years ago just became urgent. A Fabric Data Agent generates queries from your column names, not your intentions. This episode pulls apart the grounding pipeline to show where accuracy lives and dies — and why the schema investment you skipped three years ago just became urgent. microsoft-fabric,data-architecture,podcast No The Function That Bills by the Row — Fabric AI Functions 25 25 The Function That Bills by the Row — Fabric AI Functions full b24aca5d-323f-4584-9016-b003fe4f237a https://share.transistor.fm/s/eac07cd7 The Function That Bills by the Row

Episode 25 • 2026-06-19 Duration: 9:01

AI Functions let you call GPT from a SELECT statement with no API key. Zero infrastructure — until you check the capacity meter. Two billing streams, no result cache, and a default model eleven days from retirement.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The pattern we keep seeing in the field
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The concrete recommended architecture
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Ticking right now, in every tenant where someone put ai_classify in a view and moved on.
  • That quiet meter in your Capacity Metrics app.
  • Pattern dictates platform. If your pattern is "enrich once, read many," AI Functions are the shortest path in Fabric right now. If that pattern drifts into "enrich on every read," you're billing the LLM like a column default.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> The Function That Bills by the Row

Episode 25 • 2026-06-19 Duration: 9:01

AI Functions let you call GPT from a SELECT statement with no API key. Zero infrastructure — until you check the capacity meter. Two billing streams, no result cache, and a default model eleven days from retirement.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The pattern we keep seeing in the field
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The concrete recommended architecture
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Ticking right now, in every tenant where someone put ai_classify in a view and moved on.
  • That quiet meter in your Capacity Metrics app.
  • Pattern dictates platform. If your pattern is "enrich once, read many," AI Functions are the shortest path in Fabric right now. If that pattern drifts into "enrich on every read," you're billing the LLM like a column default.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 19 Jun 2026 10:00:00 +0200 Matthias Falland Matthias Falland 542 AI Functions let you call GPT from a SELECT statement with no API key. Zero infrastructure — until you check the capacity meter. Two billing streams, no result cache, and a default model eleven days from retirement. AI Functions let you call GPT from a SELECT statement with no API key. Zero infrastructure — until you check the capacity meter. Two billing streams, no result cache, and a default model eleven days from retirement. microsoft-fabric,data-architecture,podcast No The AI That Doesn't Send an Invoice — Copilot in Fabric 24 24 The AI That Doesn't Send an Invoice — Copilot in Fabric full f2a5e9de-abcf-41a1-9101-6dfb33b19eeb https://share.transistor.fm/s/5637ffa7 The AI That Doesn't Send an Invoice

Episode 24 • 2026-06-12 Duration: 9:11

Copilot in Fabric has no per-user license fee. But every request draws from the same capacity pool as your pipelines and reports. We dig into what 'included' actually costs — and when it throttles production.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • The concrete recommended architecture
  • When the rejected approach is actually right
  • Where the obvious answer breaks
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, there's an F2 running Copilot for a whole team.
  • The most expensive support ticket you'll ever file is the one where the answer is "rename your columns.
  • Pattern dictates platform. And with Copilot, the pattern is this — it's a productivity tool that's already wired into your cost structure whether you planned for it or not. The teams that get value from it are the ones who treat enablement...

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> The AI That Doesn't Send an Invoice

Episode 24 • 2026-06-12 Duration: 9:11

Copilot in Fabric has no per-user license fee. But every request draws from the same capacity pool as your pipelines and reports. We dig into what 'included' actually costs — and when it throttles production.

What we discuss

  • How it actually works underneath the abstraction
  • The pattern we keep seeing in the field
  • A real Reddit/Microsoft Q&A question unpacked
  • F-SKU realism — what this actually costs
  • The concrete recommended architecture
  • When the rejected approach is actually right
  • Where the obvious answer breaks
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, there's an F2 running Copilot for a whole team.
  • The most expensive support ticket you'll ever file is the one where the answer is "rename your columns.
  • Pattern dictates platform. And with Copilot, the pattern is this — it's a productivity tool that's already wired into your cost structure whether you planned for it or not. The teams that get value from it are the ones who treat enablement...

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 12 Jun 2026 10:00:00 +0200 Matthias Falland Matthias Falland 552 Copilot in Fabric has no per-user license fee. But every request draws from the same capacity pool as your pipelines and reports. We dig into what 'included' actually costs — and when it throttles production. Copilot in Fabric has no per-user license fee. But every request draws from the same capacity pool as your pipelines and reports. We dig into what 'included' actually costs — and when it throttles production. microsoft-fabric,data-architecture,podcast No When Autolog Stops Logging — Fabric Experiments 23 23 When Autolog Stops Logging — Fabric Experiments full 709bf89c-ea6d-41d3-bd81-c2e014e884e2 https://share.transistor.fm/s/d9ec805e When Autolog Stops Logging

Episode 23 • 2026-06-05 Duration: 8:47

Fabric's MLflow autologging promises zero-effort experiment tracking — until you train with LightGBM or XGBoost and discover your metrics column is blank. We pull apart the framework gap, the compounding exclusive flag, and the Git backup that isn't one.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The pattern we keep seeing in the field
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The concrete recommended architecture
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, a training run just finished.
  • And name your runs. Pass run_name to start_run. Forty runs all called Run followed by a number, and the comparison pane becomes useless regardless of how clean the rest of your tracking is.
  • The takeaway I'd leave anyone starting with Fabric Experiments — the abstraction is real, but it has seams you need to know on day one.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> When Autolog Stops Logging

Episode 23 • 2026-06-05 Duration: 8:47

Fabric's MLflow autologging promises zero-effort experiment tracking — until you train with LightGBM or XGBoost and discover your metrics column is blank. We pull apart the framework gap, the compounding exclusive flag, and the Git backup that isn't one.

What we discuss

  • How it actually works underneath the abstraction
  • Where the obvious answer breaks
  • A real Reddit/Microsoft Q&A question unpacked
  • The pattern we keep seeing in the field
  • Risks of the recommended path
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • The concrete recommended architecture
  • The architectural principle to take home

Key takeaways

  • Somewhere right now, a training run just finished.
  • And name your runs. Pass run_name to start_run. Forty runs all called Run followed by a number, and the comparison pane becomes useless regardless of how clean the rest of your tracking is.
  • The takeaway I'd leave anyone starting with Fabric Experiments — the abstraction is real, but it has seams you need to know on day one.

Resources

About the show

AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

This podcast was generated by AI.

Brand design based on fabricperiodictable.com.

]]> Fri, 05 Jun 2026 10:00:00 +0200 Matthias Falland Matthias Falland 528 Fabric's MLflow autologging promises zero-effort experiment tracking — until you train with LightGBM or XGBoost and discover your metrics column is blank. We pull apart the framework gap, the compounding exclusive flag, and the Git backup that isn't one. Fabric's MLflow autologging promises zero-effort experiment tracking — until you train with LightGBM or XGBoost and discover your metrics column is blank. We pull apart the framework gap, the compounding exclusive flag, and the Git backup that isn't one. microsoft-fabric,data-architecture,podcast No Your Endpoint Falls Asleep After Five Minutes — Fabric ML Models 22 22 Your Endpoint Falls Asleep After Five Minutes — Fabric ML Models full 68c085f3-2759-472f-adfc-2c5255e1e27c https://share.transistor.fm/s/9433aea1 ML Models in Fabric: Training, Deployment, and When to Stay on Azure ML

Episode 22 • 2026-05-29

Microsoft Fabric ships its own MLflow registry — but is it a replacement for Azure Machine Learning? Matthias and Fabia work through the four-layer registry model, PREDICT versus Model Endpoints, the Direct Lake prediction loop, and the architectural question that actually determines the answer: where do your predictions land?

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Where do the predictions land. That question answers the architecture. OneLake plus Power BI Direct Lake — Fabric ML Model, genuinely the right call. REST API for an app — evaluate Endpoints maturity or route to Azure ML. GPU training,...
  • I'd go further. Already on Databricks with Unity Catalog? Don't migrate. Fabric ML Model is not a migration target for Databricks shops — the platform maturity gap is real. The hybrid that actually works: train on Azure ML with GPU,...
  • For Power BI shops — yes. PREDICT writes predictions to a Delta table in OneLake, Direct Lake reads it with zero copy, zero scheduled refresh. That eliminates an entire class of ETL work. But only if Power BI is your audience.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> ML Models in Fabric: Training, Deployment, and When to Stay on Azure ML

Episode 22 • 2026-05-29

Microsoft Fabric ships its own MLflow registry — but is it a replacement for Azure Machine Learning? Matthias and Fabia work through the four-layer registry model, PREDICT versus Model Endpoints, the Direct Lake prediction loop, and the architectural question that actually determines the answer: where do your predictions land?

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Where do the predictions land. That question answers the architecture. OneLake plus Power BI Direct Lake — Fabric ML Model, genuinely the right call. REST API for an app — evaluate Endpoints maturity or route to Azure ML. GPU training,...
  • I'd go further. Already on Databricks with Unity Catalog? Don't migrate. Fabric ML Model is not a migration target for Databricks shops — the platform maturity gap is real. The hybrid that actually works: train on Azure ML with GPU,...
  • For Power BI shops — yes. PREDICT writes predictions to a Delta table in OneLake, Direct Lake reads it with zero copy, zero scheduled refresh. That eliminates an entire class of ETL work. But only if Power BI is your audience.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 29 May 2026 10:00:00 +0200 Matthias Falland Matthias Falland 526 Fabric ML Model wraps an MLflow registry inside your workspace — batch scoring to Power BI with zero refresh sounds ideal. But the real-time endpoints are Preview, Git tracks metadata only, and there's no GPU. When does this actually replace Azure ML, and when does it just sit next to it? Fabric ML Model wraps an MLflow registry inside your workspace — batch scoring to Power BI with zero refresh sounds ideal. But the real-time endpoints are Preview, Git tracks metadata only, and there's no GPU. When does this actually replace Azure ML, and microsoft-fabric,data-architecture,podcast No The Contract That Drops Your Data — Fabric Schema Registry 21 21 The Contract That Drops Your Data — Fabric Schema Registry full b04d11fb-5c23-4695-bf52-7571d3b44b8a https://share.transistor.fm/s/93a95735 Event Schema Set: Contracts That Stop Midnight Breakage

Episode 21 • 2026-05-22

Event Schema Set is Fabric's contract layer for streaming data — but it ships in Preview with real gaps. Matthias and Fabia unpack the retrofit trap, the dead-letter gap everyone worries about, and when Confluent Schema Registry is honestly the better call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Treat schemas as append-only contracts. Add fields with defaults — safe. Remove required fields — breaks consumers. Change a type — silent data corruption. Rename a field — silent loss in KQL queries. The system won't stop you. Your...
  • Fair argument. And honestly? If you're an existing Kafka shop with established Confluent practices — use Confluent. The migration cost isn't worth it. Eventstream can deserialize Confluent-encoded payloads natively. You get Avro plus JSON...
  • But you operate a separate cluster. Separate auth. Separate billing. If your entire stack is Fabric-native — Eventstream, Notebook, Activator, Eventhouse — the integration is a real win. No client library. No external cluster. Governance...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Event Schema Set: Contracts That Stop Midnight Breakage

Episode 21 • 2026-05-22

Event Schema Set is Fabric's contract layer for streaming data — but it ships in Preview with real gaps. Matthias and Fabia unpack the retrofit trap, the dead-letter gap everyone worries about, and when Confluent Schema Registry is honestly the better call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Treat schemas as append-only contracts. Add fields with defaults — safe. Remove required fields — breaks consumers. Change a type — silent data corruption. Rename a field — silent loss in KQL queries. The system won't stop you. Your...
  • Fair argument. And honestly? If you're an existing Kafka shop with established Confluent practices — use Confluent. The migration cost isn't worth it. Eventstream can deserialize Confluent-encoded payloads natively. You get Avro plus JSON...
  • But you operate a separate cluster. Separate auth. Separate billing. If your entire stack is Fabric-native — Eventstream, Notebook, Activator, Eventhouse — the integration is a real win. No client library. No external cluster. Governance...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 22 May 2026 10:00:00 +0200 Matthias Falland Matthias Falland 626 Fabric's Schema Registry promises type-safe streaming pipelines. But non-conforming events vanish without a dead-letter queue, compatibility checks don't exist, and you can't retrofit schema mode on a running Eventstream. We dig into what the contract actually enforces — and what it silently doesn't. Fabric's Schema Registry promises type-safe streaming pipelines. But non-conforming events vanish without a dead-letter queue, compatibility checks don't exist, and you can't retrofit schema mode on a running Eventstream. We dig into what the contract act microsoft-fabric,data-architecture,podcast No The Stop Button That Doesn't Stop — Data Activator 20 20 The Stop Button That Doesn't Stop — Data Activator full e1d6e6e9-34d6-4982-94ea-0582b50fb73d https://share.transistor.fm/s/e2936fa0 Data Activator: Stateful Alerts That Don't Spam Your Team

Episode 20 • 2026-05-15

Data Activator is Fabric's no-code event detection engine — but most teams build it wrong. Matthias and Fabia unpack the stateful rule model, the billing trap everyone hits once, and when Power Automate is actually the better answer.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Take-home: the entity hierarchy is the product.
  • Fair. For low-frequency data — a daily KPI check — it works fine. Where it breaks: ten thousand events per second per rule. Power Automate isn't built for that volume. And a per-flow variable isn't per-object state — you'd need one flow...
  • Right. Wrong in exactly one place — the state machine. Here's the thing. A stateless rule fires on every matching event. Value greater than twenty-five? Sensor reports every five seconds, stays above twenty-five for an hour — you get seven...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Data Activator: Stateful Alerts That Don't Spam Your Team

Episode 20 • 2026-05-15

Data Activator is Fabric's no-code event detection engine — but most teams build it wrong. Matthias and Fabia unpack the stateful rule model, the billing trap everyone hits once, and when Power Automate is actually the better answer.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Take-home: the entity hierarchy is the product.
  • Fair. For low-frequency data — a daily KPI check — it works fine. Where it breaks: ten thousand events per second per rule. Power Automate isn't built for that volume. And a per-flow variable isn't per-object state — you'd need one flow...
  • Right. Wrong in exactly one place — the state machine. Here's the thing. A stateless rule fires on every matching event. Value greater than twenty-five? Sensor reports every five seconds, stays above twenty-five for an hour — you get seven...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 15 May 2026 10:00:00 +0200 Matthias Falland Matthias Falland 553 Fabric Activator's no-code alerting looks clean on the surface. But the entity model underneath hides a billing mechanic that catches every team once: a Stop button that doesn't stop the meter. We pull it apart. Fabric Activator's no-code alerting looks clean on the surface. But the entity model underneath hides a billing mechanic that catches every team once: a Stop button that doesn't stop the meter. We pull it apart. microsoft-fabric,data-architecture,podcast No The Alert That Saved Successfully — Real-Time Dashboard 19 19 The Alert That Saved Successfully — Real-Time Dashboard full ea0dd392-c996-493a-b20b-8ae6ec7fd4be https://share.transistor.fm/s/8cee4b6f Real-Time Dashboard: When 10-Second Refresh Changes the Architecture

Episode 19 • 2026-05-08

Real-Time Dashboard is not Power BI wearing a different hat. Matthias and Fabia unpack the naming collision, permission separation, Activator alert traps, and when you should actually use Power BI DirectQuery instead.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • If someone asks 'what's happening right now' — Real-Time Dashboard.
  • But you lose permission separation. You lose tile-as-query simplicity. And your team will absolutely blame the network when the DirectQuery report takes four seconds to load at scale. Different tools, different tradeoffs.
  • Fair argument. Power BI can connect to KQL via DirectQuery. You get DAX measures, RLS, the full semantic model. And in Premium, automatic page refresh goes as low as five seconds. So if your team already lives in Power BI — that's a legitimate path.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Real-Time Dashboard: When 10-Second Refresh Changes the Architecture

Episode 19 • 2026-05-08

Real-Time Dashboard is not Power BI wearing a different hat. Matthias and Fabia unpack the naming collision, permission separation, Activator alert traps, and when you should actually use Power BI DirectQuery instead.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • If someone asks 'what's happening right now' — Real-Time Dashboard.
  • But you lose permission separation. You lose tile-as-query simplicity. And your team will absolutely blame the network when the DirectQuery report takes four seconds to load at scale. Different tools, different tradeoffs.
  • Fair argument. Power BI can connect to KQL via DirectQuery. You get DAX measures, RLS, the full semantic model. And in Premium, automatic page refresh goes as low as five seconds. So if your team already lives in Power BI — that's a legitimate path.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 08 May 2026 10:00:00 +0200 Matthias Falland Matthias Falland 634 Real-Time Dashboard puts an alert button on every tile and confirms the save every time. We trace how the Kusto-native monitoring surface actually queries, how its permission model quietly separates viewing from querying, and where the alerting pipeline silently stops evaluating. Real-Time Dashboard puts an alert button on every tile and confirms the save every time. We trace how the Kusto-native monitoring surface actually queries, how its permission model quietly separates viewing from querying, and where the alerting pipeline s microsoft-fabric,data-architecture,podcast No The Catalog Nobody Asked For — Real-Time Hub 18 18 The Catalog Nobody Asked For — Real-Time Hub full c0be697d-5089-4447-a6e4-0a39bbb24553 https://share.transistor.fm/s/ec1e37f0 Real-Time Hub: The Yellow Pages Your Streams Were Missing

Episode 18 • 2026-05-01

Matthias and Fabia unpack Fabric's Real-Time Hub — the tenant-wide catalog that sits above Eventstream, Eventhouse, and Activator. They tackle why it feels redundant until it doesn't, dig into a real Reddit question about skipping the Hub entirely, and lay out the four-layer real-time stack every architect should internalize.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • So — today's lesson. The Hub is not a processing engine. It's not a new Eventstream. It's the inventory layer that streaming has always been missing. Pattern dictates platform — if your pattern is discovery at organizational scale, this is...
  • I mean, fair question. If every stream you have lives in one workspace and one team owns them all — the Hub's discoverability value is close to zero. You already know what exists. Same if you're publishing streams to non-Fabric consumers...
  • Right. And... that's actually fine for small setups. The connector list is identical — same Azure Event Hubs tile, same Kafka tile, same CDC tiles. Both paths end up creating an eventstream artifact. But here's the thing. Eventstream is...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Real-Time Hub: The Yellow Pages Your Streams Were Missing

Episode 18 • 2026-05-01

Matthias and Fabia unpack Fabric's Real-Time Hub — the tenant-wide catalog that sits above Eventstream, Eventhouse, and Activator. They tackle why it feels redundant until it doesn't, dig into a real Reddit question about skipping the Hub entirely, and lay out the four-layer real-time stack every architect should internalize.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • So — today's lesson. The Hub is not a processing engine. It's not a new Eventstream. It's the inventory layer that streaming has always been missing. Pattern dictates platform — if your pattern is discovery at organizational scale, this is...
  • I mean, fair question. If every stream you have lives in one workspace and one team owns them all — the Hub's discoverability value is close to zero. You already know what exists. Same if you're publishing streams to non-Fabric consumers...
  • Right. And... that's actually fine for small setups. The connector list is identical — same Azure Event Hubs tile, same Kafka tile, same CDC tiles. Both paths end up creating an eventstream artifact. But here's the thing. Eventstream is...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 01 May 2026 10:00:00 +0200 Matthias Falland Matthias Falland 559 Real-Time Hub puts the same twenty-five connectors in a second UI nobody requested. We dig into why this auto-provisioned catalog becomes load-bearing the moment streams outlive their builders — and the Activator cost trap hiding behind every alert. Real-Time Hub puts the same twenty-five connectors in a second UI nobody requested. We dig into why this auto-provisioned catalog becomes load-bearing the moment streams outlive their builders — and the Activator cost trap hiding behind every alert. microsoft-fabric,data-architecture,podcast No The KQL Function Call Nobody Writes — KQL Queryset 17 17 The KQL Function Call Nobody Writes — KQL Queryset full ef2be0a0-ccd0-4dea-8ca4-d6a196ee39c0 https://share.transistor.fm/s/3c26bfe9 KQL Queryset: Why Pipe-Forward Beats SQL for Time-Series

Episode 17 • 2026-04-24 Duration: 9:39

Matthias and Fabia explore the KQL Queryset in Microsoft Fabric — why the pipe-forward mental model beats SQL for time-series data, when to use make-series vs bin+summarize, and the architectural decision between KQL Queryset, Notebooks, and the SQL endpoint.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • So — the lesson. Show me the query pattern. That's it. Don't pick your tool based on what you know. Pick it based on what the data needs. If you're doing time-series at scale, learn the pipe. It's worth it.
  • I mean, fair question. If your workload is analytical reporting — quarterly trends, executive dashboards, scheduled refresh — Power BI connected through the SQL endpoint is probably the better path. You get a richer visualization library,...
  • Right. And the naive answer is — just use the T-SQL endpoint, it supports SELECT statements. Which is true. But here's the thing. T-SQL on a KQL database is read-only DQL. SELECT only. No DDL, no management commands. And more importantly —...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> KQL Queryset: Why Pipe-Forward Beats SQL for Time-Series

Episode 17 • 2026-04-24 Duration: 9:39

Matthias and Fabia explore the KQL Queryset in Microsoft Fabric — why the pipe-forward mental model beats SQL for time-series data, when to use make-series vs bin+summarize, and the architectural decision between KQL Queryset, Notebooks, and the SQL endpoint.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • So — the lesson. Show me the query pattern. That's it. Don't pick your tool based on what you know. Pick it based on what the data needs. If you're doing time-series at scale, learn the pipe. It's worth it.
  • I mean, fair question. If your workload is analytical reporting — quarterly trends, executive dashboards, scheduled refresh — Power BI connected through the SQL endpoint is probably the better path. You get a richer visualization library,...
  • Right. And the naive answer is — just use the T-SQL endpoint, it supports SELECT statements. Which is true. But here's the thing. T-SQL on a KQL database is read-only DQL. SELECT only. No DDL, no management commands. And more importantly —...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 24 Apr 2026 10:00:00 +0200 Matthias Falland Matthias Falland 606 Most teams learn KQL through the explain keyword, which translates their SQL into syntactically correct KQL — and stops at the subset SQL can express. We trace the structural gap between bin-plus-summarize and make-series, and why the anomaly detection most teams never reach is one operator away. Most teams learn KQL through the explain keyword, which translates their SQL into syntactically correct KQL — and stops at the subset SQL can express. We trace the structural gap between bin-plus-summarize and make-series, and why the anomaly detection mo microsoft-fabric,data-architecture,podcast No The Ten-Year Cache Nobody Configured — KQL Database 16 16 The Ten-Year Cache Nobody Configured — KQL Database full 5f1d7b27-6aa9-46f9-a392-d3f6701d9001 https://share.transistor.fm/s/7518f72b KQL Database: Why Time-Series Data Needs Its Own Engine

Episode 16 • 2026-04-17 Duration: 10:26

Matthias and Fabia explore why KQL Database exists alongside four other analytical stores in Microsoft Fabric. They unpack the Eventhouse-as-building mental model, the caching vs retention trap, and when you should — and shouldn't — choose KQL over SQL.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • If your data is time-series, logs, or telemetry — and your queries are always filtered by time — KQL Database isn't just an option.
  • Fair. And honestly, if your team has strong Python skills and your latency tolerance is minutes, not milliseconds — Lakehouse plus notebooks is a legitimate path. You get the Spark ecosystem, ML libraries, broader tooling. I wouldn't fight...
  • Right. And that matters for the reversal. Because the naive answer teams land on is: just put your IoT data in the Lakehouse. Delta Lake handles everything, right?

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> KQL Database: Why Time-Series Data Needs Its Own Engine

Episode 16 • 2026-04-17 Duration: 10:26

Matthias and Fabia explore why KQL Database exists alongside four other analytical stores in Microsoft Fabric. They unpack the Eventhouse-as-building mental model, the caching vs retention trap, and when you should — and shouldn't — choose KQL over SQL.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • If your data is time-series, logs, or telemetry — and your queries are always filtered by time — KQL Database isn't just an option.
  • Fair. And honestly, if your team has strong Python skills and your latency tolerance is minutes, not milliseconds — Lakehouse plus notebooks is a legitimate path. You get the Spark ecosystem, ML libraries, broader tooling. I wouldn't fight...
  • Right. And that matters for the reversal. Because the naive answer teams land on is: just put your IoT data in the Lakehouse. Delta Lake handles everything, right?

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 17 Apr 2026 10:00:00 +0200 Matthias Falland Matthias Falland 584 Every KQL Database ships with ten years of hot SSD cache enabled by default. We dig into why Fabric needs a separate engine for time-series data, untangle the two policy knobs that control cost and performance, and explain the configuration mistake that turns an efficient store into an expensive one. Every KQL Database ships with ten years of hot SSD cache enabled by default. We dig into why Fabric needs a separate engine for time-series data, untangle the two policy knobs that control cost and performance, and explain the configuration mistake that t microsoft-fabric,data-architecture,podcast No The Green Light That Lies to You — Fabric Eventstream 15 15 The Green Light That Lies to You — Fabric Eventstream full 777e8b62-069c-4dbf-8f93-c3b331cb836c https://share.transistor.fm/s/063778e2 Eventstreams — When No-Code Streaming Hides the Failure Mode

Episode 15 • 2026-04-10 Duration: 8:03

Matthias and Fabia break down Fabric Eventstreams — the visual stream processor that replaces three Azure services with one canvas. They explore why green doesn't always mean flowing, tackle Kafka compatibility from a real Reddit question, and walk through the four billing meters that confuse every FinOps team.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Eventstreams are not about replacing Spark or Kafka.
  • Fair. If you need stateful ML inference mid-stream, Eventstreams won't do it — route to a Spark Notebook destination instead. And if your team needs exactly-once semantics, at-least-once with deduplication in Eventhouse covers most cases,...
  • And your team will absolutely say that in the sprint demo.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Eventstreams — When No-Code Streaming Hides the Failure Mode

Episode 15 • 2026-04-10 Duration: 8:03

Matthias and Fabia break down Fabric Eventstreams — the visual stream processor that replaces three Azure services with one canvas. They explore why green doesn't always mean flowing, tackle Kafka compatibility from a real Reddit question, and walk through the four billing meters that confuse every FinOps team.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Eventstreams are not about replacing Spark or Kafka.
  • Fair. If you need stateful ML inference mid-stream, Eventstreams won't do it — route to a Spark Notebook destination instead. And if your team needs exactly-once semantics, at-least-once with deduplication in Eventhouse covers most cases,...
  • And your team will absolutely say that in the sprint demo.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 10 Apr 2026 10:00:00 +0200 Matthias Falland Matthias Falland 622 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. 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. microsoft-fabric,data-architecture,podcast No The Meter That Runs Between Your Queries — Fabric Eventhouse 14 14 The Meter That Runs Between Your Queries — Fabric Eventhouse full 6494a615-4194-4346-9673-3f43193b4bcd https://share.transistor.fm/s/2b145b59 Eventhouse — Why Your Lakehouse Can't Do Real-Time

Episode 14 • 2026-04-03 Duration: 7:32

Matthias and Fabia break down Microsoft Fabric's Eventhouse — when you need a dedicated real-time store, how hot and cold cache tiers drive your bill, and why the default cache policy is the most common Eventhouse mistake.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Don't default your real-time data into the Lakehouse just because it's familiar.
  • Completely. If your latency tolerance is five to thirty seconds and you already know Spark — that's a defensible architecture. Eventhouse costs you KQL ramp-up, a separate billing model, one more item to govern. Don't add an engine just...
  • Right. Now — the naive answer when someone asks 'where do I put streaming data in Fabric' is always the Lakehouse. Everything goes to OneLake. Sounds clean on a slide.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Eventhouse — Why Your Lakehouse Can't Do Real-Time

Episode 14 • 2026-04-03 Duration: 7:32

Matthias and Fabia break down Microsoft Fabric's Eventhouse — when you need a dedicated real-time store, how hot and cold cache tiers drive your bill, and why the default cache policy is the most common Eventhouse mistake.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • The architectural principle to take home

Key takeaways

  • Don't default your real-time data into the Lakehouse just because it's familiar.
  • Completely. If your latency tolerance is five to thirty seconds and you already know Spark — that's a defensible architecture. Eventhouse costs you KQL ramp-up, a separate billing model, one more item to govern. Don't add an engine just...
  • Right. Now — the naive answer when someone asks 'where do I put streaming data in Fabric' is always the Lakehouse. Everything goes to OneLake. Sounds clean on a slide.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 03 Apr 2026 10:00:00 +0200 Matthias Falland Matthias Falland 624 Every KQL database in Fabric ships with a ten-year hot cache default nobody reviews. This episode breaks down how Eventhouse billing actually works, the UpTime meter, the cache storage tiers, and the configuration choices that separate a well-tuned real-time engine from an unexpected invoice. Every KQL database in Fabric ships with a ten-year hot cache default nobody reviews. This episode breaks down how Eventhouse billing actually works, the UpTime meter, the cache storage tiers, and the configuration choices that separate a well-tuned real-t microsoft-fabric,data-architecture,podcast No The Three Nodes That Never Sleep — Apache Airflow Job 13 13 The Three Nodes That Never Sleep — Apache Airflow Job full cf3492a7-25ca-4d27-91a8-030f794dfc38 https://share.transistor.fm/s/7eda720c Apache Airflow in Fabric: When Code-First Orchestration Earns Its Keep

Episode 13 • 2026-03-27 Duration: 8:19

When should you reach for Apache Airflow Job instead of Data Pipelines in Microsoft Fabric? Matthias and Fabia break down pool types, cost traps, dbt fragility, and the architectural threshold where visual orchestration breaks down.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • I'm stealing that. But yeah — match the orchestrator to the orchestration complexity. If your workflow fits on a visual canvas, keep it there. Airflow is for when Python is genuinely the clearest way to express your pipeline logic.
  • For maybe... sixty, seventy percent of Fabric workloads, Data Pipeline is the right answer. Airflow earns its spot when you need cross-cloud orchestration, dbt models, complex dependency graphs, or your team already thinks in Python DAGs....
  • You just paid for a permanent orchestra conductor to wave a baton at six musicians who already know the song.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Apache Airflow in Fabric: When Code-First Orchestration Earns Its Keep

Episode 13 • 2026-03-27 Duration: 8:19

When should you reach for Apache Airflow Job instead of Data Pipelines in Microsoft Fabric? Matthias and Fabia break down pool types, cost traps, dbt fragility, and the architectural threshold where visual orchestration breaks down.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • I'm stealing that. But yeah — match the orchestrator to the orchestration complexity. If your workflow fits on a visual canvas, keep it there. Airflow is for when Python is genuinely the clearest way to express your pipeline logic.
  • For maybe... sixty, seventy percent of Fabric workloads, Data Pipeline is the right answer. Airflow earns its spot when you need cross-cloud orchestration, dbt models, complex dependency graphs, or your team already thinks in Python DAGs....
  • You just paid for a permanent orchestra conductor to wave a baton at six musicians who already know the song.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 27 Mar 2026 09:00:00 +0100 Matthias Falland Matthias Falland 615 Apache Airflow Job brings code-first orchestration into Fabric with Python DAGs — but its always-on compute model means three nodes running around the clock. When does that tradeoff justify itself, and when is a Data Pipeline the honest answer? Apache Airflow Job brings code-first orchestration into Fabric with Python DAGs — but its always-on compute model means three nodes running around the clock. When does that tradeoff justify itself, and when is a Data Pipeline the honest answer? microsoft-fabric,data-architecture,podcast No Why Moving Less Data Costs More — Fabric Copy Job 12 12 Why Moving Less Data Costs More — Fabric Copy Job full d06e2bd3-2ff4-4a91-9306-3fed956afc26 https://share.transistor.fm/s/eb985641 Copy Job: When Built-In State Management Beats Pipeline Plumbing

Episode 12 • 2026-03-20 Duration: 9:54

Copy Job fills the gap between Mirroring's zero-config simplicity and Pipeline's full orchestration control. We break down the architecture, the 2x incremental pricing controversy, V-Order performance traps, and when you should still reach for Pipeline Copy Activity instead.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Take-home principle. Copy Job is Copy Activity with built-in memory. Same engine, same connectors — it just remembers where it left off. Start with a full load to validate your schema. Switch to incremental once you trust it. And always —...
  • And that's the counterpoint to the counterpoint.
  • Fair question. For a team that already has mature pipeline patterns — control tables, parameterized watermarks, solid error handling — that is a legitimate choice. You pay one-point-five CU across the board and get ForEach loops,...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Copy Job: When Built-In State Management Beats Pipeline Plumbing

Episode 12 • 2026-03-20 Duration: 9:54

Copy Job fills the gap between Mirroring's zero-config simplicity and Pipeline's full orchestration control. We break down the architecture, the 2x incremental pricing controversy, V-Order performance traps, and when you should still reach for Pipeline Copy Activity instead.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Take-home principle. Copy Job is Copy Activity with built-in memory. Same engine, same connectors — it just remembers where it left off. Start with a full load to validate your schema. Switch to incremental once you trust it. And always —...
  • And that's the counterpoint to the counterpoint.
  • Fair question. For a team that already has mature pipeline patterns — control tables, parameterized watermarks, solid error handling — that is a legitimate choice. You pay one-point-five CU across the board and get ForEach loops,...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 20 Mar 2026 09:00:00 +0100 Matthias Falland Matthias Falland 638 Copy Job promises Pipeline power with Mirroring simplicity. But incremental mode charges double the CU rate, and that's before V-Order compression and per-table rounding stack on top. We do the maths. Copy Job promises Pipeline power with Mirroring simplicity. But incremental mode charges double the CU rate, and that's before V-Order compression and per-table rounding stack on top. We do the maths. microsoft-fabric,data-architecture,podcast No Zero ETL, Thirty Times the Price — SQL Database in Fabric 11 11 Zero ETL, Thirty Times the Price — SQL Database in Fabric full c1697adf-6a1d-4025-a748-b9eb47871d33 https://share.transistor.fm/s/152b2a8a SQL Database in Fabric — When OLTP Meets Your CU Budget

Episode 11 • 2026-03-13 Duration: 9:50

SQL Database in Fabric promises zero-ETL translytical architecture — OLTP writes mirrored to OneLake automatically. But the 15-minute billing window and interactive CU consumption change the math. We break down when it makes sense and when Azure SQL Database plus mirroring is the smarter play.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's... a genuinely good architecture. For a lot of teams, that's the right call. You lose zero-config mirroring — you set it up manually — and you lose Git integration and the GraphQL API. But you gain VNet support, CDC, Always...
  • Every. Single. Time. Plus the engine startup needs a two-gig minimum memory allocation. On an F2 capacity, that's... roughly your entire capacity eaten by one database.
  • Technically — yes, that works. But the failure mode I asked about? It's cost. When you create a SQL Database in Fabric, two items appear — the database and a SQL analytics endpoint. Both consume interactive CUs. Not background —...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> SQL Database in Fabric — When OLTP Meets Your CU Budget

Episode 11 • 2026-03-13 Duration: 9:50

SQL Database in Fabric promises zero-ETL translytical architecture — OLTP writes mirrored to OneLake automatically. But the 15-minute billing window and interactive CU consumption change the math. We break down when it makes sense and when Azure SQL Database plus mirroring is the smarter play.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's... a genuinely good architecture. For a lot of teams, that's the right call. You lose zero-config mirroring — you set it up manually — and you lose Git integration and the GraphQL API. But you gain VNet support, CDC, Always...
  • Every. Single. Time. Plus the engine startup needs a two-gig minimum memory allocation. On an F2 capacity, that's... roughly your entire capacity eaten by one database.
  • Technically — yes, that works. But the failure mode I asked about? It's cost. When you create a SQL Database in Fabric, two items appear — the database and a SQL analytics endpoint. Both consume interactive CUs. Not background —...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 13 Mar 2026 09:00:00 +0100 Matthias Falland Matthias Falland 606 SQL Database in Fabric promises OLTP and analytics from one database with zero ETL. But the interactive CU billing model makes that promise expensive on small capacities. We break down exactly where the math works and where it doesn't. SQL Database in Fabric promises OLTP and analytics from one database with zero ETL. But the interactive CU billing model makes that promise expensive on small capacities. We break down exactly where the math works and where it doesn't. microsoft-fabric,data-architecture,podcast No The Fifteen-Minute Blind Spot — SQL Analytics Endpoint 10 10 The Fifteen-Minute Blind Spot — SQL Analytics Endpoint full 65cf19ef-9deb-4ab4-bc92-2d030e685a2c https://share.transistor.fm/s/f98cfe40 SQL Analytics Endpoint: Read-Only by Design

Episode 10 • 2026-03-06 Duration: 10:53

The SQL Analytics Endpoint gives you T-SQL on Lakehouse data for free — but free comes with metadata sync delays, no Git integration, and silent Direct Lake fallbacks. Matthias and Fabia unpack when to use it, when to reach for a Warehouse instead, and how to avoid the traps that catch most teams.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • So — the take-home. The SQL Analytics Endpoint is a projection, not a database. Use it for what it does brilliantly — SQL access to Delta tables with zero data duplication. But the moment you create your first view, the moment you need...
  • Fair point. And for teams that are SQL-first — BI developers, analysts who live in T-SQL — the Warehouse-only approach has real merit. You lose the zero-setup convenience, you manage a separate item, you pay for writes. But you gain...
  • Hm, let me think... because free has a price. The endpoint runs a background metadata sync process that pauses after fifteen minutes of inactivity. Your next query wakes it up, but now you're waiting for a full resync. And if you've got a...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> SQL Analytics Endpoint: Read-Only by Design

Episode 10 • 2026-03-06 Duration: 10:53

The SQL Analytics Endpoint gives you T-SQL on Lakehouse data for free — but free comes with metadata sync delays, no Git integration, and silent Direct Lake fallbacks. Matthias and Fabia unpack when to use it, when to reach for a Warehouse instead, and how to avoid the traps that catch most teams.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • So — the take-home. The SQL Analytics Endpoint is a projection, not a database. Use it for what it does brilliantly — SQL access to Delta tables with zero data duplication. But the moment you create your first view, the moment you need...
  • Fair point. And for teams that are SQL-first — BI developers, analysts who live in T-SQL — the Warehouse-only approach has real merit. You lose the zero-setup convenience, you manage a separate item, you pay for writes. But you gain...
  • Hm, let me think... because free has a price. The endpoint runs a background metadata sync process that pauses after fifteen minutes of inactivity. Your next query wakes it up, but now you're waiting for a full resync. And if you've got a...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 06 Mar 2026 09:00:00 +0100 Matthias Falland Matthias Falland 642 The SQL analytics endpoint gives every lakehouse instant T-SQL access. But the metadata sync pauses after fifteen minutes of quiet, on the default sync there's no way to check freshness from T-SQL, and views silently switch Power BI from Direct Lake to DirectQuery. The read window that goes dark when you look away. The SQL analytics endpoint gives every lakehouse instant T-SQL access. But the metadata sync pauses after fifteen minutes of quiet, on the default sync there's no way to check freshness from T-SQL, and views silently switch Power BI from Direct Lake to Di microsoft-fabric,data-architecture,podcast No The SQL Endpoint That Can't Write Back — Fabric Warehouse 9 9 The SQL Endpoint That Can't Write Back — Fabric Warehouse full 1362cd0f-f414-44af-b8be-80777e2c12ca https://share.transistor.fm/s/c72db6a0 Fabric Warehouse vs. Lakehouse: Same Storage, Different Engines

Episode 9 • 2026-02-27 Duration: 15:34

Matthias and Fabia dissect the Warehouse-vs-Lakehouse decision. They explore why three SQL options exist in Fabric, when the SQL endpoint's read-only design saves you, and why judging Warehouse performance on a cold-cache first query is the mistake everyone makes.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Today's takeaway. Warehouse and Lakehouse aren't competing products. They're different engines on the same storage. Pick based on workload pattern — T-SQL, multi-table transactions, auto-optimization means Warehouse. Spark, ML,...
  • Fair. And honestly, for a lot of teams that works. If your reporting is read-only — dashboards, DirectLake — the SQL endpoint handles it fine. In a team of eight under cost pressure, Lakehouse plus SQL endpoint might be all you need. The...
  • Right. So here's where people get it wrong. The naive answer is — Warehouse is for SQL people, Lakehouse is for Spark people. Pick your tribe. But that's way too simple. The real difference isn't the language you write. It's who owns the...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fabric Warehouse vs. Lakehouse: Same Storage, Different Engines

Episode 9 • 2026-02-27 Duration: 15:34

Matthias and Fabia dissect the Warehouse-vs-Lakehouse decision. They explore why three SQL options exist in Fabric, when the SQL endpoint's read-only design saves you, and why judging Warehouse performance on a cold-cache first query is the mistake everyone makes.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Today's takeaway. Warehouse and Lakehouse aren't competing products. They're different engines on the same storage. Pick based on workload pattern — T-SQL, multi-table transactions, auto-optimization means Warehouse. Spark, ML,...
  • Fair. And honestly, for a lot of teams that works. If your reporting is read-only — dashboards, DirectLake — the SQL endpoint handles it fine. In a team of eight under cost pressure, Lakehouse plus SQL endpoint might be all you need. The...
  • Right. So here's where people get it wrong. The naive answer is — Warehouse is for SQL people, Lakehouse is for Spark people. Pick your tribe. But that's way too simple. The real difference isn't the language you write. It's who owns the...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 27 Feb 2026 09:00:00 +0100 Matthias Falland Matthias Falland 658 Warehouse and Lakehouse store Delta tables in the same OneLake, in the same format but under separate item paths. Matthias and Fabia trace the sole-writer constraint that makes Warehouse auto-compact while Lakehouse accumulates orphaned Parquet files, and settle when each artifact earns its place. Warehouse and Lakehouse store Delta tables in the same OneLake, in the same format but under separate item paths. Matthias and Fabia trace the sole-writer constraint that makes Warehouse auto-compact while Lakehouse accumulates orphaned Parquet files, and microsoft-fabric,data-architecture,podcast No The Button That Says 'Mirror All Data' — and Doesn't | Fabric Mirroring 8 8 The Button That Says 'Mirror All Data' — and Doesn't | Fabric Mirroring full f12b979d-e33f-4c73-8eba-9f5b1f66185f https://share.transistor.fm/s/039698e8 Mirrored Databases: When Zero-Code Replication Meets Real Architecture

Episode 8 • 2026-02-20 Duration: 8:18

Matthias and Fabia explore Fabric mirrored databases — the sweet spot between real-time eventstreams and batch ETL. They unpack CDC replication, the 500-table limit, schema change risks, and why setup simplicity doesn't excuse you from data modeling.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Today's takeaway — mirroring is the sweet spot between real-time eventstreams and batch ETL.
  • Now — let me steel-man the alternative. Hm, let me think... If your analytics can tolerate live remote queries, shortcuts are genuinely better. No data copy, no replication lag, no storage cost. In a team of eight under cost pressure,...
  • Kind of, yeah. The trap is skipping the data modeling conversation because setup was easy. You still need a medallion layer on top. Mirror gives you bronze — that's it. And your team will absolutely blame the mirror when queries are slow,...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Mirrored Databases: When Zero-Code Replication Meets Real Architecture

Episode 8 • 2026-02-20 Duration: 8:18

Matthias and Fabia explore Fabric mirrored databases — the sweet spot between real-time eventstreams and batch ETL. They unpack CDC replication, the 500-table limit, schema change risks, and why setup simplicity doesn't excuse you from data modeling.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Today's takeaway — mirroring is the sweet spot between real-time eventstreams and batch ETL.
  • Now — let me steel-man the alternative. Hm, let me think... If your analytics can tolerate live remote queries, shortcuts are genuinely better. No data copy, no replication lag, no storage cost. In a team of eight under cost pressure,...
  • Kind of, yeah. The trap is skipping the data modeling conversation because setup was easy. You still need a medallion layer on top. Mirror gives you bronze — that's it. And your team will absolutely blame the mirror when queries are slow,...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 20 Feb 2026 09:00:00 +0100 Matthias Falland Matthias Falland 653 Fabric mirrored databases promise zero-code, near-real-time replication from SQL Server, Cosmos DB, and Snowflake. Matthias and Fabia pull apart what CDC actually does under the hood, discover the replication is free but the queries aren't, and trace the specific schema changes that break your mirror without telling you. Fabric mirrored databases promise zero-code, near-real-time replication from SQL Server, Cosmos DB, and Snowflake. Matthias and Fabia pull apart what CDC actually does under the hood, discover the replication is free but the queries aren't, and trace the microsoft-fabric,data-architecture,podcast No The Pipeline That Succeeded at Nothing — Fabric Data Pipelines 7 7 The Pipeline That Succeeded at Nothing — Fabric Data Pipelines full e5a39d2c-13b9-4708-9384-ceba5a4e0836 https://share.transistor.fm/s/ab710e2c Data Pipelines: When Orchestration Helps and When It Hurts

Episode 7 • 2026-02-13 Duration: 9:53

Matthias and Fabia debate when Fabric Data Pipelines earn their complexity. They unpack the orchestra-conductor mental model, walk through a real green-checkmark-but-no-data failure, and steel-man the case for skipping pipelines entirely.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's it. One activity, no dependencies — schedule it directly. Multiple steps with conditional logic — pipeline. But always validate outputs. Never trust the green checkmark without checking row counts.
  • Completely fair. If you have existing ADF, keep using it. ADF connects to Fabric natively — orchestrate Fabric items from ADF, no problem. You get the richer connector library, managed private endpoints today, event-based triggers. For...
  • And your team will absolutely add a pipeline anyway because it feels more 'enterprise.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Data Pipelines: When Orchestration Helps and When It Hurts

Episode 7 • 2026-02-13 Duration: 9:53

Matthias and Fabia debate when Fabric Data Pipelines earn their complexity. They unpack the orchestra-conductor mental model, walk through a real green-checkmark-but-no-data failure, and steel-man the case for skipping pipelines entirely.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's it. One activity, no dependencies — schedule it directly. Multiple steps with conditional logic — pipeline. But always validate outputs. Never trust the green checkmark without checking row counts.
  • Completely fair. If you have existing ADF, keep using it. ADF connects to Fabric natively — orchestrate Fabric items from ADF, no problem. You get the richer connector library, managed private endpoints today, event-based triggers. For...
  • And your team will absolutely add a pipeline anyway because it feels more 'enterprise.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 13 Feb 2026 09:00:00 +0100 Matthias Falland Matthias Falland 672 Matthias and Fabia dissect the most common pipeline failure in Fabric — a green checkmark on a pipeline that loaded zero rows. They trace how control flow success semantics hide empty runs, build the validation architecture that catches them, and steel-man the case for skipping pipelines entirely. Matthias and Fabia dissect the most common pipeline failure in Fabric — a green checkmark on a pipeline that loaded zero rows. They trace how control flow success semantics hide empty runs, build the validation architecture that catches them, and steel-ma microsoft-fabric,data-architecture,podcast No The 3 AM Variable — Spark Job Definitions 6 6 The 3 AM Variable — Spark Job Definitions full 2003e0ed-3b53-45a4-9980-62d9a9919a75 https://share.transistor.fm/s/d2099fc9 Spark Job Definitions: Notebooks Are for Humans, SJDs Are for Machines

Episode 6 • 2026-02-06 Duration: 10:23

Matthias and Fabia break down Spark Job Definitions in Microsoft Fabric — the production wrapper most teams skip until their scheduled notebook fails at 3 AM. They cover the notebook-to-SJD promotion path, why state leakage kills overnight runs, retry policies, and when a plain notebook schedule is actually fine.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • And wrap it in a Pipeline. Even if just for the alerts.
  • Fair. Solo workflows where the output includes visualizations — scheduled notebook is the right call. The line I draw: the moment a second person depends on that output, or it feeds a downstream system, promote it. Solo analyst with a...
  • Every SJD run starts clean. No leftover variables, no stale session. That's — I mean, that's the whole point. Reproducibility by design, not by discipline.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Spark Job Definitions: Notebooks Are for Humans, SJDs Are for Machines

Episode 6 • 2026-02-06 Duration: 10:23

Matthias and Fabia break down Spark Job Definitions in Microsoft Fabric — the production wrapper most teams skip until their scheduled notebook fails at 3 AM. They cover the notebook-to-SJD promotion path, why state leakage kills overnight runs, retry policies, and when a plain notebook schedule is actually fine.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • And wrap it in a Pipeline. Even if just for the alerts.
  • Fair. Solo workflows where the output includes visualizations — scheduled notebook is the right call. The line I draw: the moment a second person depends on that output, or it feeds a downstream system, promote it. Solo analyst with a...
  • Every SJD run starts clean. No leftover variables, no stale session. That's — I mean, that's the whole point. Reproducibility by design, not by discipline.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 06 Feb 2026 09:00:00 +0100 Matthias Falland Matthias Falland 577 A scheduled notebook that intermittently fails with 'variable not defined' is actually the lucky outcome. The unlucky one runs with stale state, produces plausible numbers, and nobody checks for a month. A scheduled notebook that intermittently fails with 'variable not defined' is actually the lucky outcome. The unlucky one runs with stale state, produces plausible numbers, and nobody checks for a month. microsoft-fabric,data-architecture,podcast No The Install Tax Nobody Counted — Fabric Environments 5 5 The Install Tax Nobody Counted — Fabric Environments full 974311a5-7333-4b1e-963c-cfbb5984f464 https://share.transistor.fm/s/0fbbb891 Spark Environments: When Your Starter Pool Isn't Enough

Episode 5 • 2026-01-30 Duration: 9:09

Matthias and Fabia dig into Spark Environments in Microsoft Fabric — the dependency management layer most teams adopt too early. They cover the Starter Pool trade-off, why publishing takes fifteen minutes, the SJD gotcha, and when percent-pip install is actually the right call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Fair. For pure experiments, percent-pip is the right call — session-scoped, instant, no friction. But across a team? Five people installing different versions every morning. No persistence between sessions. And good luck getting consistent...
  • They just added fifteen minutes to every first session for zero benefit.
  • Because of the publish step. When you create or update an Environment, Fabric resolves every dependency, downloads packages, builds what's basically a container image, and distributes it to compute nodes. That takes five to fifteen...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Spark Environments: When Your Starter Pool Isn't Enough

Episode 5 • 2026-01-30 Duration: 9:09

Matthias and Fabia dig into Spark Environments in Microsoft Fabric — the dependency management layer most teams adopt too early. They cover the Starter Pool trade-off, why publishing takes fifteen minutes, the SJD gotcha, and when percent-pip install is actually the right call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Fair. For pure experiments, percent-pip is the right call — session-scoped, instant, no friction. But across a team? Five people installing different versions every morning. No persistence between sessions. And good luck getting consistent...
  • They just added fifteen minutes to every first session for zero benefit.
  • Because of the publish step. When you create or update an Environment, Fabric resolves every dependency, downloads packages, builds what's basically a container image, and distributes it to compute nodes. That takes five to fifteen...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 30 Jan 2026 09:00:00 +0100 Matthias Falland Matthias Falland 561 Every team that skips Fabric Environments ends up running %pip install on every scheduled notebook, every session, every day. The twelve-minute publish everyone complains about turns out to be the cheapest line item in the Spark budget. Every team that skips Fabric Environments ends up running %pip install on every scheduled notebook, every session, every day. The twelve-minute publish everyone complains about turns out to be the cheapest line item in the Spark budget. microsoft-fabric,data-architecture,podcast No The Lakehouse You Never Created — Dataflow Gen2 4 4 The Lakehouse You Never Created — Dataflow Gen2 full 37373579-0ff2-4546-b63a-2302a881555e https://share.transistor.fm/s/e9210312 Dataflow Gen2: When Power Query Meets Enterprise Scale

Episode 4 • 2026-01-23 Duration: 11:20

Matthias and Fabia unpack Dataflow Gen2 — the low-code transformation layer in Fabric. They cover staging architecture, the Gen1-to-Gen2 leap, why your dataflow is slow, multi-destination patterns, and when you should skip the visual editor entirely and reach for a notebook.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Low-code where you can, full-code where you must.
  • Completely fair. And for teams with strong engineering backgrounds, notebooks are often the right call. But — here's the thing. Not every team has five Python engineers. I've worked with organizations where the data people are Excel and...
  • They get Gen1 performance on a Gen2 label.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Dataflow Gen2: When Power Query Meets Enterprise Scale

Episode 4 • 2026-01-23 Duration: 11:20

Matthias and Fabia unpack Dataflow Gen2 — the low-code transformation layer in Fabric. They cover staging architecture, the Gen1-to-Gen2 leap, why your dataflow is slow, multi-destination patterns, and when you should skip the visual editor entirely and reach for a notebook.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Low-code where you can, full-code where you must.
  • Completely fair. And for teams with strong engineering backgrounds, notebooks are often the right call. But — here's the thing. Not every team has five Python engineers. I've worked with organizations where the data people are Excel and...
  • They get Gen1 performance on a Gen2 label.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 23 Jan 2026 09:00:00 +0100 Matthias Falland Matthias Falland 566 Every Dataflow Gen2 silently provisions a staging Lakehouse behind the familiar Power Query interface. We dig into the execution architecture, explain why query folding decides your performance, and settle when a notebook is the honest answer. Every Dataflow Gen2 silently provisions a staging Lakehouse behind the familiar Power Query interface. We dig into the execution architecture, explain why query folding decides your performance, and settle when a notebook is the honest answer. microsoft-fabric,data-architecture,podcast No Why Your Notebook Breaks at 2 AM — Fabric Notebooks 3 3 Why Your Notebook Breaks at 2 AM — Fabric Notebooks full 5713c684-cbb7-4233-a63d-25466dd0afcf https://share.transistor.fm/s/412382a8 Fabric Notebooks: When Interactive Spark Meets Production Reality

Episode 3 • 2026-01-16 Duration: 11:26

Matthias and Fabia dig into Fabric Notebooks — the code-first data engineering workhorse. They cover starter pools vs. custom environments, the new native Python mode, the notebook-to-production gap, and why your notebook that runs perfectly at 2pm crashes in the pipeline at 2am.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Completely fair. And I'll go further — I've seen teams spin up Spark to process ten megabytes of CSV. That's like renting a crane to hang a picture frame. If your transformation is row-level, SQL-expressible, and under a gig? A warehouse...
  • Nope. It's one or the other. And your team will absolutely discover this at the worst possible moment — usually during a demo. The play is: develop and explore on starter pools, switch to a custom Environment only for final testing and...
  • And teams do exactly that. Until they need great_expectations, or dbt-core, or some internal package. Starter pools give you the default library set — pandas, scikit-learn, plotly, the usual. But the moment you need anything custom, you...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fabric Notebooks: When Interactive Spark Meets Production Reality

Episode 3 • 2026-01-16 Duration: 11:26

Matthias and Fabia dig into Fabric Notebooks — the code-first data engineering workhorse. They cover starter pools vs. custom environments, the new native Python mode, the notebook-to-production gap, and why your notebook that runs perfectly at 2pm crashes in the pipeline at 2am.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • Completely fair. And I'll go further — I've seen teams spin up Spark to process ten megabytes of CSV. That's like renting a crane to hang a picture frame. If your transformation is row-level, SQL-expressible, and under a gig? A warehouse...
  • Nope. It's one or the other. And your team will absolutely discover this at the worst possible moment — usually during a demo. The play is: develop and explore on starter pools, switch to a custom Environment only for final testing and...
  • And teams do exactly that. Until they need great_expectations, or dbt-core, or some internal package. Starter pools give you the default library set — pandas, scikit-learn, plotly, the usual. But the moment you need anything custom, you...

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 16 Jan 2026 09:00:00 +0100 Matthias Falland Matthias Falland 604 Fabric notebooks feel like a simple coding environment, but underneath there's a distributed system with a driver node boundary nobody warned you about. We unpack what actually changes when a pipeline takes over — and when graduation to a Spark Job Definition is worth the cleanup. Fabric notebooks feel like a simple coding environment, but underneath there's a distributed system with a driver node boundary nobody warned you about. We unpack what actually changes when a pipeline takes over — and when graduation to a Spark Job Defini microsoft-fabric,data-architecture,podcast No The Folder That Isn't There — OneLake Shortcuts 2 2 The Folder That Isn't There — OneLake Shortcuts full 02ca7707-bf81-4cfd-bae9-21fbbcc3437e https://share.transistor.fm/s/4bdfd1b7 OneLake Shortcuts: Virtual Pointers, Real Tradeoffs

Episode 2 • 2026-01-09 Duration: 9:21

Matthias and Fabia break down OneLake shortcuts — virtual pointers that unify multi-cloud data without copies. They cover the read-write boundary, the shared credential security model, caching economics, and when a good old copy is actually the better architecture call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's it. Don't shortcut the architecture thinking just because the feature is called Shortcut.
  • Completely fair. And in plenty of cases, that IS the right answer. I mean, architecture is not religion — if a nightly copy gives you better performance, lower cost, and simpler security? Do that. Shortcuts shine when data governance says...
  • Security model. External shortcuts use stored credentials — one credential, shared by everyone who accesses that shortcut. That's a fundamentally different security posture than internal shortcuts, where your own identity passes through....

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> OneLake Shortcuts: Virtual Pointers, Real Tradeoffs

Episode 2 • 2026-01-09 Duration: 9:21

Matthias and Fabia break down OneLake shortcuts — virtual pointers that unify multi-cloud data without copies. They cover the read-write boundary, the shared credential security model, caching economics, and when a good old copy is actually the better architecture call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's it. Don't shortcut the architecture thinking just because the feature is called Shortcut.
  • Completely fair. And in plenty of cases, that IS the right answer. I mean, architecture is not religion — if a nightly copy gives you better performance, lower cost, and simpler security? Do that. Shortcuts shine when data governance says...
  • Security model. External shortcuts use stored credentials — one credential, shared by everyone who accesses that shortcut. That's a fundamentally different security posture than internal shortcuts, where your own identity passes through....

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 09 Jan 2026 09:00:00 +0100 Matthias Falland Matthias Falland 639 OneLake shortcuts promise a unified namespace without moving data. But the abstraction hides a split security model, a deletion path that reaches across workspaces, and caching economics that quietly shift the bill. OneLake shortcuts promise a unified namespace without moving data. But the abstraction hides a split security model, a deletion path that reaches across workspaces, and caching economics that quietly shift the bill. microsoft-fabric,data-architecture,podcast No The File Count Nobody's Watching — Fabric Lakehouse 1 1 The File Count Nobody's Watching — Fabric Lakehouse full a3418f0d-d33e-4d85-b789-3f08c4bd3112 https://share.transistor.fm/s/7ec54440 Lakehouse Architecture: One Storage Layer, Zero Excuses

Episode 1 • 2026-01-02 Duration: 8:32

Why the Fabric Lakehouse isn't a set-and-forget data platform. Matthias and Fabia unpack the real architectural tradeoffs — medallion layers, Delta table maintenance, Direct Lake, and when a Warehouse is actually the better call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's the whole lesson. Don't architect for the demo. Architect for month six.
  • Completely valid choice. If your team is SQL-first, no Spark needed, no ML — the Warehouse might genuinely be the better call. Pick the tool that matches the team and the workload, not the one that looks most impressive on the architecture slide.
  • Fair. Not a trap — a tradeoff. You get Spark, flexibility, streaming and batch in one place. But you own the maintenance. That's the deal.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Lakehouse Architecture: One Storage Layer, Zero Excuses

Episode 1 • 2026-01-02 Duration: 8:32

Why the Fabric Lakehouse isn't a set-and-forget data platform. Matthias and Fabia unpack the real architectural tradeoffs — medallion layers, Delta table maintenance, Direct Lake, and when a Warehouse is actually the better call.

What we discuss

  • A real-world mistake from a pre-Fabric era
  • The one question that reframes the architectural debate
  • How we got here — predecessor products and evolution
  • Why the "obvious" answer is often wrong
  • A real Reddit/Microsoft Q&A question unpacked
  • The concrete recommended architecture
  • F-SKU realism — what this actually costs
  • When the rejected approach is actually right
  • Risks of the recommended path
  • What Microsoft is shipping that changes the calculus
  • The architectural principle to take home

Key takeaways

  • That's the whole lesson. Don't architect for the demo. Architect for month six.
  • Completely valid choice. If your team is SQL-first, no Spark needed, no ML — the Warehouse might genuinely be the better call. Pick the tool that matches the team and the workload, not the one that looks most impressive on the architecture slide.
  • Fair. Not a trap — a tradeoff. You get Spark, flexibility, streaming and batch in one place. But you own the maintenance. That's the deal.

Resources

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Fri, 02 Jan 2026 09:00:00 +0100 Matthias Falland Matthias Falland 513 Every write to a Delta table leaves Parquet files behind. There's a hard cap per SKU — and on the recommended Direct Lake mode, exceeding it doesn't degrade your reports. It kills them. The Lakehouse maintenance bill nobody budgeted for. Every write to a Delta table leaves Parquet files behind. There's a hard cap per SKU — and on the recommended Direct Lake mode, exceeding it doesn't degrade your reports. It kills them. The Lakehouse maintenance bill nobody budgeted for. microsoft-fabric,data-architecture,podcast No Welcome to the Fabric Architecture Podcast Welcome to the Fabric Architecture Podcast trailer 3062c3f4-1b2b-41dd-9c46-e2a8e05dcc17 https://share.transistor.fm/s/0a41c9e5 Welcome to the Fabric Architecture Podcast

Episode 0 • 2026-01-01 Duration: 3:41

Meet Matthias Falland and his AI co-host Fabia. Learn what this show is — anonymized real customer architecture decisions, cost realism, counter-arguments included — and what it is not. Weekly episodes, aligned with Fabric Friday recordings.

Key principles of the show

  • Architecture is not religion.
  • Pattern dictates platform.
  • Simplicity on the slide is not simplicity at runtime.
  • In a team of eight under cost pressure...

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Welcome to the Fabric Architecture Podcast

Episode 0 • 2026-01-01 Duration: 3:41

Meet Matthias Falland and his AI co-host Fabia. Learn what this show is — anonymized real customer architecture decisions, cost realism, counter-arguments included — and what it is not. Weekly episodes, aligned with Fabric Friday recordings.

Key principles of the show

  • Architecture is not religion.
  • Pattern dictates platform.
  • Simplicity on the slide is not simplicity at runtime.
  • In a team of eight under cost pressure...

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.

]]> Thu, 01 Jan 2026 09:00:00 +0100 Matthias Falland Matthias Falland 222 Meet Matthias Falland and his AI co-host Fabia. Learn what this show is — anonymized real customer architecture decisions, cost realism, counter-arguments included — and what it is not. Weekly episodes, aligned with Fabric Friday recordings. Meet Matthias Falland and his AI co-host Fabia. Learn what this show is — anonymized real customer architecture decisions, cost realism, counter-arguments included — and what it is not. Weekly episodes, aligned with Fabric Friday recordings. microsoft-fabric,data-architecture,podcast No