知识卡片
宏观架构连接状态与逻辑
宏观架构把系统看作组件或服务及其交互:存储跨请求的长期状态、处理请求或触发事件,再把逻辑和状态组合成用例。先复用数据库、队列、负载均衡等积木,服务实现缺失功能或填补积木之间的不匹配。设计须同时考虑协调、一致状态、安全、可用性与扩展,而非只画服务清单。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构导论 · 查看原书依据
A distributed architecture must be able to store long-living data, sometimes across multiple requests; process user requests, either in response to direct requests or some kind of a trigger; and combine the state and logic to carry out the user requests efficiently. Macro architecture sees the systems as units (components or services) and their interactions.
参考来源
- 位置:《Software Architecture and Decision-Making》第5章《宏观架构导论》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch05.xhtml)
- 结论依据:原文的定义、比较或例子支持“宏观架构把系统看作组件或服务及其交互:存储跨请求的长期状态、处理请求或触发事件,再把逻辑和状态组合成用例”;正文据此说明用途和边界。
- 原始内容:A distributed architecture must be able to store long-living data, sometimes across multiple requests; process user requests, either in response to direct requests or some kind of a trigger; and combine the state and logic to carry out the user requests efficiently. Macro architecture sees the systems as units (components or services) and their interactions.