知识卡片
新范式须核实规模能力
从原书案例可推得一项选型检查:采用不成熟的技术栈前,以目标数据量、对象粒度和并发负载核实其能力,并确认团队有处理边界问题的经验。原书回顾的早期对象数据库项目在测试数据阶段已占用显著容量;团队后来发现现成基础设施扩展不足、细粒度对象存储成本高、对象依赖纠缠引发事务争用,最终耗费数月补救。这是作者所述项目经历,不能外推为所有对象数据库的性能结论。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第05章|Modeling Paradigms · 查看原书依据
In the early 1990s, this project committed itself to several cutting-edge technologies, including use of an object-oriented database on a large scale.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第42章《原书第05章|Modeling Paradigms》(源文件:_epub-src/0321125215_ch05lev1sec6.html)
- 结论依据:原文以早期项目经历列出容量、对象存储成本与依赖争用三项问题,并说明修复耗时;卡片只将其作为选型风险案例。
- 原始内容(早期项目情节):A story from an object-oriented project of only a decade ago illustrates the risks of working in an immature paradigm. In the early 1990s, this project committed itself to several cutting-edge technologies, including use of an object-oriented database on a large scale. [...] But gradually the realization crept upon us that we were beginning to absorb a significant fraction of the database's capacity—with test data! The actual database would be dozens of times larger. The actual transaction volume would be dozens of times higher. (原 EPUB 在 `capacity` 后以异常 U+0097 表示破折号,此处只规范该字符;`[...]` 略去同段中间的项目介绍。)
- 原始内容(三项原因与修复):There were three sources of the problem. First, the off-the-shelf infrastructure provided with the database simply didn't scale up to our needs. Second, storage of fine-grained objects turned out to be much more costly than we had realized. Third, parts of the object model had such a tangle of interdependencies that contention became a problem with a relatively small number of concurrent transactions. With the help of this hired expert, we enhanced the infrastructure. The team, now aware of the impact of fine-grained objects, began to find models that worked better with this technology. All of us deepened our thinking about the importance of limiting the web of relationships in a model, and we began applying this new understanding to making better models with more decoupling between closely interrelated aggregates. Several months were lost in this recovery, in addition to the earlier months spent going down a failed path. And this had not been the team's first setback resulting from the immaturity of the chosen technologies and our own lack of experience with the associated learning curve.