← 返回刚才阅读的位置

知识卡片

结构图卡 · 2313.e.5.i

模块化单体按领域组织代码

理解等级:初级

模块化单体把一个部署单元内的功能按业务领域或子领域分成模块。客户资料模块可同时包含表示和业务代码,层次只是模块内部的次级划分;这与[[分层架构按技术职责分组]]先按技术职责切开各业务的做法不同。模块是代码和职责边界,并不天然是独立进程。

结构图:

flowchart TD
    App[单一部署单元] --> Customer[客户领域模块]
    App --> Order[订单领域模块]
    Customer --> CP[表示与业务职责]
    Order --> OP[表示与业务职责]
这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • The Modular Monolith Architecture Style · 查看原书依据

      Because modular monolith is considered a domain-partitioned architecture (one organized by business domains rather than technical capabilities), its isomorphic shape is defined as a single deployment unit with functionality grouped by domain area.

    参考来源

    - 位置:《Fundamentals of Software Architecture》原书第11章《The Modular Monolith Architecture Style》(阅读计划第14项;源文件:`OEBPS/ch11.html`) - 结论依据:原文把模块化单体定义为单部署单元、按领域分组,并与分层技术分区比较。 - 原始内容:Because modular monolith is considered a domain-partitioned architecture (one organized by business domains rather than technical capabilities), its isomorphic shape is defined as a single deployment unit with functionality grouped by domain area .