知识卡片

普通读书笔记卡 · 3291

维护痛点可提示API切入点

理解等级:中级

某子系统若变更失败多、支持工单多、代码频繁改动且复杂度高,可成为引入 API 边界和渐进替换的候选。指标只是线索,还要查明是职责混杂、测试缺失还是局部实现问题,再决定拆分或先修内部设计。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • · 查看原书依据

      Consider adding code quality metrics as this can provide a rough guide to potential underlying issues. A maintenance issue or subsystem issue could be a good opportunity to introduce an API abstraction to pull functionality out and use strangler fig to drive improvement. It might also be a code smell that good coding principles are not followed. In Chapter 9 we will also consider how

    参考来源

    - 位置:《Mastering API Architecture》第8章《Redesigning Applications to API-Driven Architectures》之《Upgrade and Maintenance Issues》(源文件:_epub-src/OEBPS/ch08.xhtml) - 结论依据:原文列出变更失败、工单、代码 churn 和复杂度等信号,建议用 API 抽象或绞杀模式改善。 - 原始内容:Consider adding code quality metrics as this can provide a rough guide to potential underlying issues. A maintenance issue or subsystem issue could be a good opportunity to introduce an API abstraction to pull functionality out and use strangler fig to drive improvement. It might also be a code smell that good coding principles are not followed. In Chapter 9 we will also consider how