架构 on Jeanphilo Bloghttps://shio-chan-dev.github.io/jeanblog/zh/categories/%E6%9E%B6%E6%9E%84/Recent content in 架构 on Jeanphilo BlogHugo -- 0.159.2zh-cnSat, 24 Jan 2026 15:29:20 +0800为什么事件驱动架构能提升可扩展性https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/event-driven-scalability/Sat, 24 Jan 2026 15:29:20 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/event-driven-scalability/解释事件驱动架构的扩展优势、适用场景与工程取舍。“喜欢这个的人也喜欢…”：电商推荐的最小实现https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/recommendation-people-also-like/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/recommendation-people-also-like/用协同过滤的简化模型实现“相似商品推荐”。80 年代后的 CPU 变化与编程影响https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cpu-changes-after-80s/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cpu-changes-after-80s/概述 CPU 从频率提升到多核与缓存层级的演进，并解释对编程的影响。除了攻击之外，哪些设计会导致拒绝服务https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-issues-causing-dos/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-issues-causing-dos/讨论架构设计缺陷如何引发类似 DoS 的系统故障。分布式系统中的故障切换与会话管理https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/failover-and-user-session/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/failover-and-user-session/解释故障切换与用户会话管理的核心策略与工程取舍。如何设计去中心化 P2P 系统：节点、发现与一致性https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-decentralized-p2p-system/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-decentralized-p2p-system/从节点发现、路由与一致性角度介绍 P2P 系统设计。统一设计是否意味着架构师的贵族统治？https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/unity-of-design-aristocracy/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/unity-of-design-aristocracy/讨论“统一设计”与团队自治之间的张力与平衡。为什么 CGI 的扩展性不好：进程模型的代价https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cgi-scalability-issues/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cgi-scalability-issues/解释 CGI 进程模型的性能瓶颈与扩展性问题。性能生命周期：从设计到上线的全流程管理https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-lifecycle-management/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-lifecycle-management/说明性能从需求、设计、开发到上线的生命周期管理要点。紧急设计 vs 演化架构：系统如何在变化中保持方向https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/emergent-vs-evolutionary-architecture/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/emergent-vs-evolutionary-architecture/对比紧急设计与演化架构的理念与工程实践。什么时候紧耦合是合理的：工程上的现实选择https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/when-tight-coupling-ok/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/when-tight-coupling-ok/讨论紧耦合的合理场景与风险控制方法。什么是 Cloud Ready：系统上云前必须具备的特征https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cloud-ready-system/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cloud-ready-system/总结云就绪系统的关键特征与工程实践清单。