Warehouses exist because transactional and analytical workloads fight each other. Operational databases are row-oriented, tuned for many small reads and writes; analytical queries scan entire columns across years of history, which is what columnar storage and massively parallel execution are built for. Running reporting against the production database is a latency incident with a date on it.
A warehouse of raw dumps is a swamp with a SQL interface. The value comes from modelling — conformed dimensions, well-defined marts, one agreed definition of "revenue" — which is unglamorous work that determines whether the organisation trusts its own numbers. The trigger for investing is usually the meeting where two teams argue from two different answers to the same question.
Cost governance is part of the architecture, because compute is metered per query or per credit. Ungoverned, a warehouse bill grows with every dashboard refresh and every analyst exploring with SELECT *; governed, workloads are isolated, queries are reviewed for the scans they cause, and storage tiers match access patterns. For AI systems the warehouse is increasingly an input — the feature source for models and, with tightly guardrailed text-to-SQL, structured context for agents.
A semantic layer has become the standard companion: one governed place where revenue, active user and churn are defined once, and every BI tool, notebook and agent reads the same definition. Without it the warehouse is internally consistent but the interpretations are not, and the organisation goes back to arguing about numbers — just with better infrastructure underneath the argument. The semantic layer also gives AI agents a governed target: text-to-SQL against defined metrics rather than raw tables.
Structure inside the warehouse follows a maturity path: raw landing tables, cleaned and conformed intermediate models, then marts shaped for consumption. Skipping the middle layer feels fast and produces marts built directly on raw sources, after which every upstream change breaks everything downstream. The cleanup costs multiples of the layering that was deferred, which is why "we will remodel it later" is one of the more expensive sentences in data engineering.
Codazz builds this in production — AI & ML Development.