知识卡片
微服务边界先于技术选型
微服务由独立服务通过明确 API 通信;成败关键仍是服务边界是否内聚、松耦合。拆分前可用领域上下文映射和事件风暴找职责边界,再挑通信技术;只把代码切小并不能自动减少依赖。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
As with classic SOA, one of the biggest challenges when designing APIs using a microservices architecture is getting the boundaries (and cohesiveness) of an API and the underlying services correct. Using techniques like context mapping and event storming from the world of DDD, before building or evolving towards microservices, will often greatly reward your future efforts. Microservice APIs should ideally use lightweight technologies that encourage
参考来源
- 位置:《Mastering API Architecture》第8章《Redesigning Applications to API-Driven Architectures》之《Microservices》(源文件:_epub-src/OEBPS/ch08.xhtml)
- 结论依据:原文将微服务描述为通过 API 通信的独立服务,并强调边界设计与领域分析。
- 原始内容:As with classic SOA, one of the biggest challenges when designing APIs using a microservices architecture is getting the boundaries (and cohesiveness) of an API and the underlying services correct. Using techniques like context mapping and event storming from the world of DDD, before building or evolving towards microservices, will often greatly reward your future efforts. Microservice APIs should ideally use lightweight technologies that encourage