Data Warehousing & BI (KA 9)

The Inmon vs Kimball debate, the modern lakehouse compromise, and the BI delivery loop.

0/1 done

Overview

Data Warehousing & BI (KA 9)

The Inmon vs Kimball debate, the modern lakehouse compromise, and the BI delivery loop.

Why it matters

The KA the business actually sees. Everything else is invisible until the dashboard loads. DMBOK organises this KA around delivery, not technology.

Going deeper

The classical debate, in one table:

ApproachBuild orderStrengthCost
Inmon (top-down)Enterprise model first → martsEnterprise consistencySlow first delivery
Kimball (bottom-up)Marts first → conformed dimensionsFast first valueRisk of inconsistent dimensions
Lakehouse + dbtRaw → staging → marts in SQL, in gitEngineering rigourRequires SQL+git discipline

Modern stacks converge on dbt + lakehouse: Kimball-style marts on top of Inmon-style staging, all version-controlled. The argument about ‘which one wins’ is mostly historical.

Analogy

A data warehouse is the cafeteria, the lake is the loading dock.

Trucks unload raw produce at the loading dock (lake) — boxes, crates, sometimes still muddy. The cafeteria (warehouse) cleans, portions, plates and serves meals — predictable, fast, ready to eat. A diner who'd rather rummage in the loading dock is welcome to; everyone else expects the cafeteria.

The lakehouse is the cafeteria and the loading dock under one roof, with the kitchen visible to both — fewer trucks, less spoilage, but the discipline of the cafeteria still has to live somewhere.

Make it stick

Anchor data warehousing & bi (ka 9) to something you actually own.

  • Where in your platform does *data warehousing & bi (ka 9)* live today — and who owns it?
  • What is the smallest version of *data warehousing & bi (ka 9)* you could ship next sprint?
  • What's the most likely misuse of *data warehousing & bi (ka 9)*, and how would you spot it in a design review?

Reading in progress · 0 of 1 activity done