Microsoft Fabric / Medallion architecture
Data-as-a-Service Pipeline
01 / Problem
Clients needed a dependable path from on-premise databases to analytics-ready data without rebuilding ingestion logic for every tenant.
02 / Architecture
03 / Key decisions
- Separated raw, refined, and serving layers to keep replay and quality checks explicit.
- Used Dataflow Gen2 and notebooks for a mix of managed movement and custom transformations.
- Designed refresh windows around full and incremental workloads.
04 / Outcome
40min full load · 5min incremental · 3 refreshes/day
05 / What I'd do differently
I would formalize tenant-level observability earlier, especially around freshness, failed partitions, and cost per refresh.