Fabric Architecture Podcast

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

Listen Later

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

      • Eventhouse overview
      • Store data in Microsoft Fabric - Decision guide
      • Caching policy (hot and cold cache)
      • Get data overview
      • KQL quick reference
      • Eventhouse and KQL Database consumption
      • Data availability in OneLake
      • Enable Eventhouse endpoint for lakehouse and data warehouse
      • Create an Eventhouse
      • Create a KQL database
      • Real-Time Intelligence tutorial
      • Change data policies
      • Cost breakdown of Eventhouse
      • Manage and monitor an eventhouse
      • Decision guide: Choose the right data store

        • 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
        View all episodesView all episodes
        Download on the App Store
        Fabric Architecture PodcastBy Matthias Falland