知识卡片
数仓集中模型的负担
数据仓库以ETL从运营系统抽取、清理、变换并加载事实维度模型,供SQL分析。企业级统一模型难满足所有用例,数据集市虽可聚焦需求,但从数仓取数仍需中央模型,直接取运营数据又使跨集市分析困难。若ETL读取私有数据库结构,内部小改动也会破坏分析任务,形成团队摩擦。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 数据网格 · 查看原书依据
The data warehouse (DWH) architecture is relatively straightforward. Extract data from all of the enterprise’s operational systems, transform the source data into an analytical model, and load the resultant data into a data analysis–oriented database. This database is the data warehouse. This data management architecture is based primarily on the extract-transform-load (ETL) scripts. The data
参考来源
- 位置:《Learning Domain-Driven Design》第16章《数据网格》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch16.html)
- 结论依据:原文展开ETL、暂存、数据集市及直接读取运营数据库所导致的模型和组织耦合。
- 原始内容:The data warehouse (DWH) architecture is relatively straightforward. Extract data from all of the enterprise’s operational systems, transform the source data into an analytical model, and load the resultant data into a data analysis–oriented database. This database is the data warehouse. This data management architecture is based primarily on the extract-transform-load (ETL) scripts. The data