知识卡片
迁移清单先按真实用例缩小范围
迁移前盘点消费者、依赖和用途;同一库可能用于缓存、数据库卸载或本地查表,不应机械替换。先将用例分类,再用小型验证选择透明替换、合并或取消迁移。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第9章《Code Migrations》(源文件:`_epub-src/OPS/ch09.xhtml`,归一化正文 [4231:8341))
- 结论依据:原文以 Ehcache 到 Redis 说明清单会发现部分用途不必迁移。
- 原始内容:Inventories are necessary to understand the problem space, we will need inventories, analysis of the use cases, and POCs. First of all, start with inventories. You might be wondering, why waste time and build an inventory, if we need to migrate anyways? Inventories are important because: Scope: Inventories allow you to understand the scope of the migration. Understand the problem: Capture important insights about your consumers, dependencies, and issues.