知识卡片

普通读书笔记卡 · 1841.h.1.a.1.a.3.f.1.a.4.a

界面代理隔离迁移

理解等级:中级

先用映射代理把界面调用与后端实现位置分离,再逐步引入服务发现,使可以迁移的部分独立替换。新增远程调用会带来延迟和可用性问题,不能把原本进程内函数直接等价搬成接口。每次分离后都应保护新集成点的契约。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Evolvable Architectures · 查看原书依据

      When developers have identified the correct service partitioning, the next step is separation of the business layers from the UI. Even in microservices architectures, the UIs often resolve back to a monolith—​after all, developers must show a unified UI at some point. Thus, developers commonly separate the UIs early in the migration, creating a mapping proxy layer between UI components and the backend services they

    参考来源

    - 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第07章《Building Evolvable Architectures》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch07.html;段落定位:creating a mapping proxy layer between UI components) - 结论依据:原文对“界面代理隔离迁移”的定义或案例,支撑“先用映射代理把界面调用与后端实现位置分离,再逐步引入服务发现,使可以迁移的部分独立替换”的归纳。据其上下文,新增远程调用会带来延迟和可用性问题,不能把原本进程内函数直接等价搬成接口。 - 原始内容:When developers have identified the correct service partitioning, the next step is separation of the business layers from the UI. Even in microservices architectures, the UIs often resolve back to a monolith—​after all, developers must show a unified UI at some point. Thus, developers commonly separate the UIs early in the migration, creating a mapping proxy layer between UI components and the backend services they