知识卡片
服务通过接口封装自己的数据
让一个服务管理自身数据,并通过明确API提供访问,避免其他服务直接依赖内部表结构。同步请求或异步事件都可成为边界。需要区分来源:本书将十二要素原“端口绑定”一节重新解释为数据隔离,这属于作者采用的扩展表述,不能冒充原始十二要素名称。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- It’s All About Dependability · 查看原书依据
Each service should be entirely self-contained. That is, it should manage its own data, and only make its data accessible only via an API designed for that purpose. If this sounds familiar to you, good! This is actually one of the core principles of microservices, which we’ll discuss more in “The Microservices System Architecture”. Very
参考来源
- 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:让一个服务管理自身数据,并通过明确API提供访问,避免其他服务直接依赖内部表结构。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:Each service should be entirely self-contained. That is, it should manage its own data, and only make its data accessible only via an API designed for that purpose. If this sounds familiar to you, good! This is actually one of the core principles of microservices, which we’ll discuss more in “The Microservices System Architecture”. Very