知识卡片
数据拆分的相反驱动
拆库不是拆服务后的必然动作。变更隔离、连接容量、扩展、故障隔离、架构量子和数据类型适配推动拆分;外键、视图等数据关系与必须整体提交的事务推动保留。应把冲突写成业务选择:是独立上线更重要,还是完整性约束更重要?共享库可让多服务同时受数据库故障影响;仅拆应用进程不能消除这种边界。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 拆分操作数据 · 查看原书依据
Architects can justify a data decomposition effort by understanding and analyzing data disintegrators (drivers that justify breaking apart data) and data integrators (drivers that justify keeping data together). Striving for a balance between these two driving forces and analyzing the trade-offs of each is the key to getting data granularity right.
参考来源
- 位置:《Software Architecture: The Hard Parts》第06章《拆分操作数据》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:Architects can justify a data decomposition effort by understanding and analyzing data disintegrators (drivers that justify breaking apart data) and data integrators (drivers that justify keeping data together). Striving for a balance between these two driving forces and analyzing the trade-offs of each is the key to getting data granularity right.