Fabric Architecture Podcast

By Matthias Falland

Architecture decisions for Microsoft Fabric. Anonymized real customer scenarios, cost realism, counter-arguments included. Weekly episodes aligned with Fabric Friday recordings.... more

Download on the App Store

Download on the App Store

Get it on Google Play

FAQs about Fabric Architecture Podcast:

How many episodes does Fabric Architecture Podcast have?

The podcast currently has 32 episodes available.

Fabric Architecture Podcast episodes:

May 22, 2026The Contract That Drops Your Data
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
Schema Registry — known limitations
CloudEvents 1.0
Use schemas in eventstreams
Real-Time Hub Schemas
Business Events Concepts
Consume Business Events from Activator
Eventhouse
Confluent Kafka source
Schema Registry in Fabric Real-Time Intelligence (preview) — Overview
Create and manage event schema sets
Create and manage event schemas in schema sets
EventSchemaSet REST API definition
Eventstream Overview — Schema Management section
Multiple-Schema Inferencing in Eventstream (Preview)
Eventstream Data Formats: JSON, CSV, Avro
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.
...more
12min
May 22, 2026The Pipeline That Succeeded at Nothing
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
Data Pipelines in Fabric
Activity Overview
Control flow activities
Pipeline Overview
Copy Activity
Parameters and Expressions
Monitor Pipeline Runs
Decision Guide: Pipeline vs Dataflow vs Spark
Data Integration Strategy Guide
Reddit r/MicrosoftFabric
MS Q&A
Stack Overflow
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.
...more
10min
May 15, 2026The Stop Button That Doesn't Stop
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
Add Activator to Eventstream
Activator from KQL Queryset
Activator from RTD
Activator from Power BI
Real-Time Hub Set Alerts
Set Alerts on Anomaly Detection
What is Fabric Activator?
Tutorial: Create and activate a Fabric Activator rule
Create a rule in Fabric Activator
Trigger modeling in Activator
Fabric Activator rules
Detection conditions
Activator Limitations
Latency in Activator
Activator Capacity Consumption
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.
...more
10min
May 15, 2026The 3 AM Variable
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
What is a Spark Job Definition?
Create SJD
Run SJD
SJD Git Integration
Pipeline SJD Activity
Streaming Data into Lakehouse
Spark Best Practices
Job Queueing
Decision Guide: Pipeline vs Dataflow vs Spark
Fabric vs Synapse Spark Comparison
MS Q&A
Reddit r/MicrosoftFabric
Stack Overflow
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.
...more
11min
May 08, 2026The Alert That Saved Successfully
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
KQL Database
KQL Queryset
Real-Time Hub
Activator on RTD
Anomaly Detection
Power BI + KQL
Fabric Map
What is Real-Time Dashboard?
Create a Real-Time Dashboard
Real-Time Dashboard Permissions
Use Parameters in Real-Time Dashboards
Customize Real-Time Dashboard Visuals
Activator Limitations
Generate Real-Time Dashboard with Copilot
Copilot-assisted Real-Time Data Exploration (Preview)
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.
...more
9min
May 08, 2026The Install Tax Nobody Counted
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
Create and manage environments
Configure Starter Pools
Manage libraries
Environments GA
Reddit r/MicrosoftFabric
MS Q&A
Stack Overflow
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.
...more
10min
May 04, 2026The Catalog Nobody Asked For
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
managed private endpoint
Eventstream Overview
KQL Database
Activator Overview
Real-Time Dashboard
Schema Sets
Digital Twin Builder
Real-Time Hub Overview
Get Started with Real-Time Hub
Supported Sources
Add Azure Event Hubs Source
Add Azure IoT Hub Source
Get Azure Blob Storage Events
Create Streams from Workspace Item Events
Create Streams from OneLake Events
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.
...more
12min
May 01, 2026The Lakehouse You Never Created
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
What is Dataflow Gen2?
Dataflow Gen2 architecture
Connector overview
Power Query M reference
Staging settings
Incremental refresh
Schedule Dataflow Gen2
Best practices
Create your first Dataflow Gen2
Monitor Dataflows
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.
...more
12min
April 24, 2026Why Your Notebook Breaks at 2 AM
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
What is a notebook?
Python experience in notebooks
Configure Starter Pools
Lakehouse and notebooks
Data Wrangler
Manage libraries
Schedule notebook
High Concurrency mode
VS Code extension
Spark Job Definition
Notebook best practices
Author and execute notebooks
Notebook visualization
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.
...more
12min
April 17, 2026The Folder That Isn't There
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
OneLake Shortcuts
Shortcut types
Where to create shortcuts
Shortcut authorization
Shortcut caching
Limitations
Shortcut security
Create OneLake Shortcut
Create ADLS Gen2 Shortcut
Create S3 Shortcut
Create GCS Shortcut
Shortcuts REST API
On-premises Shortcuts
Dataverse Shortcuts
OneLake Overview
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.
...more
10min

FAQs about Fabric Architecture Podcast:

How many episodes does Fabric Architecture Podcast have?

The podcast currently has 32 episodes available.