← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 5362

架构与数据双向决策

理解等级:高级

架构划分决定哪些服务能够访问或修改哪些数据,数据的所有权、访问要求和分析用途也会反过来限制服务边界。取舍分析要从这两个方向检查:只画服务框而不处理写入责任与运营、分析数据的分离,容易把困难留给后续集成。书中方法是显露相互约束及其代价,再针对具体问题选择,而不是给所有系统一个统一边界。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 前言:困难来自相互制约的取舍 · 查看原书依据

      We took all the examples and worked through them like architects, applying trade-off analysis for each situation, but also paying attention to the process we used to arrive at the trade-offs. One of our early revelations was the increasing importance of data in architecture decisions: who can/should access data, who can/should write to it, and how to manage the separation of analytical and operational data. To that end, we asked experts in those fields to join us, which allows this book to fully incorporate decision making from both angles: architecture to data and data to architecture.

    参考来源

    - 位置:《Software Architecture: The Hard Parts》Preface(来源项目book-sources,源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/preface01.xhtml) - 结论依据:原文说明下述关系或机制;本卡保留其实际论域,不将书中描述扩展成当前外部验证。 - 原始内容:We took all the examples and worked through them like architects, applying trade-off analysis for each situation, but also paying attention to the process we used to arrive at the trade-offs. One of our early revelations was the increasing importance of data in architecture decisions: who can/should access data, who can/should write to it, and how to manage the separation of analytical and operational data. To that end, we asked experts in those fields to join us, which allows this book to fully incorporate decision making from both angles: architecture to data and data to architecture.