知识卡片

普通读书笔记卡 · 2276.m.15.a

盈利机会不等于复杂软件

理解等级:高级

营销枢纽被视为新的利润机会,真正的竞争力来自现有客户关系和合同,而配套软件的业务逻辑很简单。按“新利润来源”直接选择事件溯源、CQRS和大量微服务,让技术复杂度超过了业务复杂度。判断软件子域时应定位竞争优势实际存在的细粒度活动;商业重要性本身不能推出复杂的建模实现是必要条件。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 附录A:应用DDD的案例 · 查看原书依据

      Despite the fact that the business considered the marketing hub to be a core subdomain, it had no technical complexity. Behind that complex architecture stood a very simple business logic, one so simple that it could have been implemented using plain active records. As it turned out, the businesspeople were looking to profit by leveraging our existing relationships with other companies, and not through the use of clever algorithms. The technical complexity ended up being much higher than the business complexity. To describe such discrepancies in complexities, we use the term accidental complexity, and our initial design ended up being exactly that. The system was overengineered.

    参考来源

    - 位置:《Learning Domain-Driven Design》附录A《Applying DDD: A Case Study》(阅读计划17)(来源项目book-sources,源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/app01.html) - 结论依据:原文在所列实例或定义中直接说明本卡讨论的关系;本卡保留相应语境和限制,不把案例结果推广成无条件规则。 - 原始内容:Despite the fact that the business considered the marketing hub to be a core subdomain, it had no technical complexity. Behind that complex architecture stood a very simple business logic, one so simple that it could have been implemented using plain active records. As it turned out, the businesspeople were looking to profit by leveraging our existing relationships with other companies, and not through the use of clever algorithms. The technical complexity ended up being much higher than the business complexity. To describe such discrepancies in complexities, we use the term accidental complexity, and our initial design ended up being exactly that. The system was overengineered.