Spark Environments: When Your Starter Pool Isn't Enough

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.