知识卡片

普通读书笔记卡 · 3334

治理应守住契约和领域

理解等级:高级

跨团队治理应统一公开契约、领域边界和必要的观测约定,让各服务自主选择实现细节。把统一要求深入框架、共享库或数据库,会牺牲独立部署和技术迁移能力。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第6章《Principles of Proper Services》(源文件:`_epub-src/OPS/ch06.xhtml`,归一化正文 [21022:25275)) - 结论依据:原文区分良好治理与差的治理:前者促进轻量一致的契约实践,后者强迫共享库和数据库进入实现层。 - 原始内容:Good governance covers best practices in your contracts, and promotes lightweight consistency and best practices; bad governance forces itself into the implementation, demanding the reuse of shared libraries and databases ( Table 6.1 ): Independence Central Governance Good Bad Good Bad Code Deployment Implementation Details Technology Choices Contracts Business Domains leading to Duplication Snowflake Monitoring Contracts Domain Mapping Observability Stack Deployment Tools Naming Database Schemas Implementation Details Table 6.1: Independence vs central governance Independence really should be a binary, ideal state: you either have it, or you do not.