知识卡片
运行时选型需要真实剖析
运行时的内存、启动、GC和调度成本要结合真实分配与I/O负载衡量。原书按语言直接推断商品服务优选JVM且Go需手工内存管理过于绝对;核验Go官方GC指南可知Go自动管理内存,仍需控制分配与资源。https://go.dev/doc/gc-guide(2026-10-23)。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Choosing Platform and Technologies · 查看原书依据
Generally, developers choose the platform that they are most comfortable in writing their code in. While that is an important criterion for long term maintainability of the application, it is worthwhile to look at different runtime platforms that exhibit distinct performance characteristics that can become critical at scale as is listed as follows:
参考来源
- 位置:《Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…》第12章《Choosing Platform and Technologies》(来源项目book-sources;源文件:extracted/Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…/_epub-src/OPS/ch12.xhtml)
- 结论依据:原文给出本卡对应定义或示例;运行时的内存、启动、GC和调度成本要结合真实分配与I/O负载衡量。 对原文省略和过度承诺的限定是本卡显式纠正,不能反过来当作原书已证明。
- 原始内容:Generally, developers choose the platform that they are most comfortable in writing their code in. While that is an important criterion for long term maintainability of the application, it is worthwhile to look at different runtime platforms that exhibit distinct performance characteristics that can become critical at scale as is listed as follows: