Lakehouse Architecture: One Storage Layer, Zero Excuses

Lakehouse Architecture: One Storage Layer, Zero Excuses Episode 1 • 2026-01-02 Duration: 8:28 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 Lakehouse end-to-end scenario Tutorial: Create a lakehouse Medallion architecture for Fabric Tutorial: Ingest data SQL analytics endpoint Direct Lake overview Delta Lake table optimization Decision guide: Lakehouse vs Warehouse High Concurrency Mode Lakehouse overview Table maintenance Work with Delta Lake tables Organize with Medallion architecture Use Apache Spark in Fabric Greenfield Lakehouse on Fabric 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.