知识卡片
业务边界决定服务职责
领域与子领域属于问题空间,模型与限界上下文属于解决空间。上下文界定一套业务术语、规则、数据与输入输出的适用范围,应尽量高内聚、低耦合。围绕业务需求而非技术层拆服务,团队才有机会独立修改完整业务能力;边界可能受遗留系统和第三方约束,不要求上下文与子领域永远一一对应。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Why Event-Driven Microservices · 查看原书依据
Domain-driven design, as coined by Eric Evans in his book of the same title, introduces some of the necessary concepts for building event-driven microservices. Given the wealth of articles, books, and blogs-of-the-month readily available to talk about this subject, I will keep this section brief.
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第01章《Why Event-Driven Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch01.xhtml;规范化段落起句:Domain-driven design, as coined)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:领域与子领域属于问题空间,模型与限界上下文属于解决空间。本卡同时保留其适用条件与失败边界。
- 原始内容:Domain-driven design, as coined by Eric Evans in his book of the same title, introduces some of the necessary concepts for building event-driven microservices. Given the wealth of articles, books, and blogs-of-the-month readily available to talk about this subject, I will keep this section brief.