知识卡片

普通读书笔记卡 · 3284

服务拆分要平衡归属与成本

理解等级:高级

面向服务架构用网络上的服务向其他组件提供能力。拆分时需同时权衡接口内聚、代码所有权和大量服务的设计及运行成本;把业务逻辑塞入网关或总线,会让中间层成为新的耦合点。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • · 查看原书依据

      Evolving your applications toward SOA can be beneficial, but care should be taken to avoid the use of frameworks or vendor middleware that promotes high coupling or low cohesions. For example, always avoid adding business logic to an API gateway or enterprise service bus (ESB). One of the biggest challenges with designing SOA-based systems is getting the size and ownership of services “correct”—i.e., striking a

    参考来源

    - 位置:《Mastering API Architecture》第8章《Redesigning Applications to API-Driven Architectures》之《Service-Oriented Architecture (SOA)》(源文件:_epub-src/OEBPS/ch08.xhtml) - 结论依据:原文说明 SOA 的服务通信方式,提醒避免中间件承载业务逻辑,并列出规模和所有权的权衡。 - 原始内容:Evolving your applications toward SOA can be beneficial, but care should be taken to avoid the use of frameworks or vendor middleware that promotes high coupling or low cohesions. For example, always avoid adding business logic to an API gateway or enterprise service bus (ESB). One of the biggest challenges with designing SOA-based systems is getting the size and ownership of services “correct”—i.e., striking a