知识卡片
模块化必须回应业务
拆系统的理由应是业务所需的上市速度和竞争优势,而非“现有补丁都没用”。把当前症状对应到可维护、可测、可部署、可扩展和容错,再说明拆分如何改善,并明确迁移成本和风险,才能形成可检验的业务论证。模块化也可在模块单体、微内核内部实现,不必一律变成分布式服务。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构模块化的业务驱动 · 查看原书依据
Architects shouldn’t break a system into smaller parts unless clear business drivers exist. The primary business drivers for breaking applications into smaller parts include speed-to-market (sometimes called time-to-market) and achieving a level of competitive advantage in the marketplace. Speed-to-market is achieved through architectural agility—the ability to respond quickly to change. Agility is a compound architectural characteristic made up of many other architecture characteristics, including maintainability, testability, and deployability.
参考来源
- 位置:《Software Architecture: The Hard Parts》第3章《架构模块化的业务驱动》(来源项目: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/ch03.xhtml)
- 结论依据:原文的定义、比较或案例支持“拆系统的理由应是业务所需的上市速度和竞争优势,而非“现有补丁都没用””;正文据此解释其用途与适用边界。
- 原始内容:Architects shouldn’t break a system into smaller parts unless clear business drivers exist. The primary business drivers for breaking applications into smaller parts include speed-to-market (sometimes called time-to-market) and achieving a level of competitive advantage in the marketplace. Speed-to-market is achieved through architectural agility—the ability to respond quickly to change. Agility is a compound architectural characteristic made up of many other architecture characteristics, including maintainability, testability, and deployability.