DWH architecture in e-commerce
Data sources ETL / ELT DWH Activation
────────────────── ─────────────── ─────────── ────────────
Website (events) ──→
CRM ──→ Transformation → BigQuery / Dashboards
ERP ──→ Cleansing → ClickHouse / ML models
POS terminals ──→ Aggregation → Snowflake / Segments
Ad platforms ──→ Redshift Reports
Common DWH solutions for e-commerce
| Solution | Strengths | Who it suits |
|---|---|---|
| Google BigQuery | Scalability, ML integration | Teams in the Google ecosystem |
| ClickHouse | Real-time analytics, open source | High-traffic sites |
| Snowflake | Simplicity, data sharing | Mid-market and enterprise |
| Azure Synapse | Integration with Power BI and the Microsoft stack | Microsoft infrastructure |
| Amazon Redshift | AWS ecosystem | AWS infrastructure |
How a DWH supports ML personalization
The DWH stores: ML models learn: Output:
───────────── ─────────────────── ──────────────────────
Transactions → Churn prediction → Churn score per user
Behaviour → Affinity model → Affinity profile
RFM features → Lifetime value → LTV forecast
Session data → Next best product → A personal recommendation
Exporting predictions out of the DWH — into the CDP and on into the personalization platform — is done through the same ETL pipelines.