Skip to content

[FAQ Bot] NEW: How do I structure a layered data warehouse (raw, clean, analytics) for #253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[FAQ Bot] NEW: How do I structure a layered data warehouse (raw, clean, analytics) for #253

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions ...ering-zoomcamp/module-3/015_a198f6959c_layered-data-warehouse-batch-pipeline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
id: a198f6959c
question: How do I structure a layered data warehouse (raw, clean, analytics) for
a batch pipeline?
sort_order: 15
---

- Raw layer: store ingested data exactly as received
- Clean layer: filter invalid records and enforce basic constraints
- Data quality (dq) layer: validate completeness and consistency (e.g. missing timestamps)
- Analytics layer: build aggregated views
- Mart layer: expose final business metrics

Flow: raw → clean → dq → analytics → mart

Each layer is implemented as SQL transformations in PostgreSQL and BigQuery.

This separation helps with debugging, testing, and ensuring that analytical outputs are built on validated data.