← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1971.o.1.c.1.a.3

Evant案例显示领域知识与柔性设计支持扩容

理解等级:高级

原书 Evant 案例:库存管理软件在投资紧缩后几乎停滞,后来大客户提出大规模规划需求。仅剩四名开发者,但他们具备领域知识、扩容经验、有效协作文化和易于修改的设计,最终让系统处理数十亿规划元素与数百用户,并赢得客户。

作者观察到收购后模型与设计仍继续演进。这是特定团队与业务条件下的实际叙述,不能仅把成功归因于领域模型。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Epilogues · 查看原书依据

      Although reduced to four developers, the team had assets. They were skilled, with knowledge of the domain, and one member had expertise in scaling issues. They had a very effective development culture. And they had a code base with a supple design that facilitated change. That summer, those four developers made a heroic development effort resulting in the ability to handle billions of planning elements and hundreds of users. On the strength of those capabilities, Evant won the behemoth client and, soon after, was bought by another company that wanted to leverage their software and their proven ability to accommodate new demands. The domain-driven design culture (as well as the Extreme Programming culture) survived the transition and was revitalized. Today, the model and design continue to evolve, far richer and suppler two years later than when I made my contribution.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第141章《Epilogues》(源文件:_epub-src/0321125215_art01lev1sec1.html) - 结论依据:原文陈述Evant面临的扩容要求、四人团队的已有条件、完成的容量与随后业务结果。 - 原始内容:Although reduced to four developers, the team had assets. They were skilled, with knowledge of the domain, and one member had expertise in scaling issues. They had a very effective development culture. And they had a code base with a supple design that facilitated change. That summer, those four developers made a heroic development effort resulting in the ability to handle billions of planning elements and hundreds of users. On the strength of those capabilities, Evant won the behemoth client and, soon after, was bought by another company that wanted to leverage their software and their proven ability to accommodate new demands. The domain-driven design culture (as well as the Extreme Programming culture) survived the transition and was revitalized. Today, the model and design continue to evolve, far richer and suppler two years later than when I made my contribution.