Architecture on Jeanphilo Bloghttps://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/Recent content in Architecture 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/总结云就绪系统的关键特征与工程实践清单。如何维护单体架构：模块化、边界与演进https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/monolith-maintenance/Sat, 24 Jan 2026 12:33:47 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/monolith-maintenance/给出单体架构的维护策略，强调模块化与边界控制。发布/订阅在可扩展性上的缺点：一致性与可观测性成本https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/publish-subscribe-cons/Sat, 24 Jan 2026 12:29:51 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/publish-subscribe-cons/分析发布/订阅模型在扩展性方面的缺点与工程成本。如何避免供应商锁定（Vendor Lock-in）：策略与实践https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/vendor-lock-in/Sat, 24 Jan 2026 12:29:51 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/vendor-lock-in/给出防止供应商锁定的工程策略，包括抽象层、可迁移架构与数据可移植性。如何设计高可扩展系统：从瓶颈到弹性https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-scalable-systems/Sat, 24 Jan 2026 12:29:51 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-scalable-systems/给出设计高可扩展系统的核心原则与实践步骤。什么是三层架构：职责划分与工程价值https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/threelayer-architecture/Sat, 24 Jan 2026 12:29:51 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/threelayer-architecture/解释三层架构的分层职责、优缺点与适用场景。C10k 问题怎么解决：高并发连接的策略https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/c10k-strategies/Sat, 24 Jan 2026 12:25:49 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/c10k-strategies/解释 C10k 的成因与解决策略，包括事件驱动、内核调优与连接管理。横向扩展 vs 纵向扩展：区别、场景与取舍https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/scale-up-vs-scale-out/Sat, 24 Jan 2026 12:25:49 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/scale-up-vs-scale-out/解释 scale up 与 scale out 的差异、适用场景与成本模型。什么是 CQRS：命令与查询职责分离https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cqrs-basics/Sat, 24 Jan 2026 12:25:49 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cqrs-basics/解释 CQRS 的核心思想、适用场景与落地成本。性能与可扩展性的关系：别把快当成能扩https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-vs-scalability/Sat, 24 Jan 2026 12:25:49 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-vs-scalability/解释性能与可扩展性的差异与关系，并给出架构决策与指标建议。缓存什么时候危险：一致性、失效与业务风险https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/caching-when-dangerous/Sat, 24 Jan 2026 12:23:30 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/caching-when-dangerous/说明缓存何时会带来风险，并给出适用条件与规避策略。Web 与桌面应用的容错管理差异：思路与实践https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/fault-tolerance-web-vs-desktop/Sat, 24 Jan 2026 11:20:31 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/fault-tolerance-web-vs-desktop/对比 Web 与桌面应用的容错管理差异，给出关键策略与实践指南。