---
title: "Practical Data Warehouse Design and Architecture Guide"
description: "The guide presents data warehouse design as a business-aligned process for building, modernizing, or scaling analytics infrastructure, rather than merely storing data. It recommends defining analytics use cases and stakeholder needs first, then organizing a three-tier architecture of source, storage, and semantic output layers; cloud designs can decouple compute and storage and use open formats. A Bronze–Silver–Gold medallion flow preserves raw lineage, applies cleansing and deduplication, and produces consumption-ready dimensional models, while retention and archival policies control sprawl. For modeling, it favors star schemas for user-facing BI, uses snowflake normalization when redundancy is material, and stresses explicit fact-table granularity, domain-owned data marts, and workload-specific refresh cadences. Governance and operations include Unity Catalog, access controls, masking, lineage, multi-region deployment, disaster recovery, and CI/CD, followed by phased rollout through high-value domains."
---

# Practical Data Warehouse Design and Architecture Guide

[Databricks](https://yomu.fyi/company/databricks) · Databricks Staff · Jun 2, 2026

**Type:** Tutorial

## Summary

The guide presents data warehouse design as a business-aligned process for building, modernizing, or scaling analytics infrastructure, rather than merely storing data. It recommends defining analytics use cases and stakeholder needs first, then organizing a three-tier architecture of source, storage, and semantic output layers; cloud designs can decouple compute and storage and use open formats. A Bronze–Silver–Gold medallion flow preserves raw lineage, applies cleansing and deduplication, and produces consumption-ready dimensional models, while retention and archival policies control sprawl. For modeling, it favors star schemas for user-facing BI, uses snowflake normalization when redundancy is material, and stresses explicit fact-table granularity, domain-owned data marts, and workload-specific refresh cadences. Governance and operations include Unity Catalog, access controls, masking, lineage, multi-region deployment, disaster recovery, and CI/CD, followed by phased rollout through high-value domains.

## Context

The guide is intended for data engineers, architects, analytics engineers, and technical leaders planning a new warehouse, migrating from a legacy system, or scaling an existing warehouse for AI. It emphasizes aligning architecture with analytics use cases, stakeholder needs, governance requirements, and operational demands.

## Approach / What changed

It lays out a three-tier architecture, zoned Bronze–Silver–Gold storage, dimensional modeling and data-mart patterns, governance controls, and operational practices including multi-region deployment, disaster recovery, and CI/CD. It recommends piloting with a high-value domain and expanding through phased rollout.

## Takeaways

- Fact-table granularity should be established early because finer granularity increases storage while maximizing analytical flexibility, and changing granularity later can require costly pipeline rewrites.
- Refresh cadence should match each data mart’s workload: the guide contrasts nightly batch updates for finance month-end close with hourly updates for marketing campaign optimization.
- Schema changes and new data-mart definitions should pass through version-controlled pull requests, automated tests, and staged environments before production deployment.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [CI/CD](https://yomu.fyi/topic/ci-cd), [Data Governance](https://yomu.fyi/topic/data-governance), [Data Warehousing](https://yomu.fyi/topic/data-warehousing)

- Source: [Databricks](https://www.databricks.com/blog/data-warehouse-design)
- Source URL: https://www.databricks.com/blog/data-warehouse-design
- Ingested by Yomu: 2026-08-31T03:32:16.659Z

[Read original post](https://www.databricks.com/blog/data-warehouse-design)