知识卡片
案例先完成服务拆分再迁云
会议系统已把参会者能力拆成服务,因而迁云时选择更换云托管数据库的平台迁移,而非再次重构。这个案例说明策略选择取决于当前架构状态和目标;网关可随后逐步把本地流量导向云端。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
this to a service early in this book, the refactor/re-architect did not appear appropriate. However, when you are adding new functionality into the conference system in the future, re-architecting the system (potentially extracting a service) and moving this to the cloud would be an option to strongly consider. Rehosting could be a solid strategy, but we are keen to take advantage of a cloud-based database-as-a-service
参考来源
- 位置:《Mastering API Architecture》第9章《Using API Infrastructure to Evolve Toward Cloud Platforms》之《Case Study: Replatforming the Attendee Service to the Cloud》(源文件:_epub-src/OEBPS/ch09.xhtml)
- 结论依据:原文逐项排除其他迁移策略,说明已抽取服务且希望使用托管数据库,并迁移网关支持渐进路由。
- 原始内容:this to a service early in this book, the refactor/re-architect did not appear appropriate. However, when you are adding new functionality into the conference system in the future, re-architecting the system (potentially extracting a service) and moving this to the cloud would be an option to strongly consider. Rehosting could be a solid strategy, but we are keen to take advantage of a cloud-based database-as-a-service