知识卡片
业务系统边界会移动
网络监听、日志、认证和消息路由等系统职责可以从应用代码移到框架、容器平台或无服务器配置中。职责转移能简化业务逻辑,但业务、展示、存储和基础设施若混为一体,会增加耦合。判断边界时要看能否独立理解和演进,而非只看代码文件属于哪一层。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 提供应用运行基础设施 · 查看原书依据
Serverless creates the opportunity to move even more system concerns out of application code and into infrastructure. For example, without serverless, a developer might write code that listens to and reads from a message queue and then writes responses to another queue. With serverless, the developer’s code doesn’t need to know where its message comes
参考来源
- 位置:《Infrastructure As Code》第13章《提供应用运行基础设施》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch13.html)
- 结论依据:原文说明网络监听、日志、认证和消息路由等系统职责可以从应用代码移到框架、容器平台或无服务器配置中;本卡据此解释其用途及适用边界。
- 原始内容:Serverless creates the opportunity to move even more system concerns out of application code and into infrastructure. For example, without serverless, a developer might write code that listens to and reads from a message queue and then writes responses to another queue. With serverless, the developer’s code doesn’t need to know where its message comes