知识卡片
架构表达应连接实时元数据
架构模型和图可从不断更新的元模型、应用登记、成本与血缘生成,减少静态文档过期。架构师仍需解释业务目标、组织设计和取舍,并用设计讨论指导团队,不能把图自动生成当作自动完成架构决策。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Putting Theory into Practice · 查看原书依据
Enterprise architects traditionally delivered their artifacts as formalized models or Visio diagrams. This craft is no longer scalable in the era of dynamic, large enterprises. In modern practice, models, blueprints, and diagrams should be constructed from the underlying metamodel, using a code repository tool. This repository should be frequently updated with data modeling and design information, cost information, lineage, new application registration, ownership registration, and
参考来源
- 位置:《Data Management at Scale》第12章《Putting Theory into Practice》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch12.html)
- 结论依据:原文对constructed from the underlying metamodel的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。
- 原始内容:Enterprise architects traditionally delivered their artifacts as formalized models or Visio diagrams. This craft is no longer scalable in the era of dynamic, large enterprises. In modern practice, models, blueprints, and diagrams should be constructed from the underlying metamodel, using a code repository tool. This repository should be frequently updated with data modeling and design information, cost information, lineage, new application registration, ownership registration, and