知识卡片
事务形成真实拆分边界
事务要求多个操作作为整体协调,形成普通类依赖图难以显示的强关联。若业务必须原子更新,服务拆分不能只看代码大小;过细边界可能把本地事务变成昂贵分布式协调。先识别真实事务上下文,再比较聚合或拆分代价。
进一步联系:[[服务拆分先大后小]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Evolutionary Data · 查看原书依据
Transactions are a special form of coupling because transactional behavior doesn’t appear in traditional technical architecture-centric tools. Architects can easily determine the afferent and efferent coupling between classes with a variety of tools. They have a much harder time determining the extent of transactional contexts. Just as coupling between schemas harms evolution, transactional coupling binds the constituent parts together in concrete ways, making evolution more
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第06章《Evolutionary Data》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch06.html;段落定位:transactional coupling binds the constituent parts together)
- 结论依据:原文对“事务形成真实拆分边界”的定义或案例,支撑“事务要求多个操作作为整体协调,形成普通类依赖图难以显示的强关联”的归纳。据其上下文,若业务必须原子更新,服务拆分不能只看代码大小;过细边界可能把本地事务变成昂贵分布式协调。
- 原始内容:Transactions are a special form of coupling because transactional behavior doesn’t appear in traditional technical architecture-centric tools. Architects can easily determine the afferent and efferent coupling between classes with a variety of tools. They have a much harder time determining the extent of transactional contexts. Just as coupling between schemas harms evolution, transactional coupling binds the constituent parts together in concrete ways, making evolution more