<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>软件架构 on Jeanphilo Blog</title><link>https://shio-chan-dev.github.io/jeanblog/zh/tags/%E8%BD%AF%E4%BB%B6%E6%9E%B6%E6%9E%84/</link><description>Recent content in 软件架构 on Jeanphilo Blog</description><generator>Hugo -- 0.159.2</generator><language>zh-cn</language><lastBuildDate>Sat, 24 Jan 2026 12:33:47 +0800</lastBuildDate><atom:link href="https://shio-chan-dev.github.io/jeanblog/zh/tags/%E8%BD%AF%E4%BB%B6%E6%9E%B6%E6%9E%84/index.xml" rel="self" type="application/rss+xml"/><item><title>如何维护单体架构：模块化、边界与演进</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/monolith-maintenance/</link><pubDate>Sat, 24 Jan 2026 12:33:47 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/monolith-maintenance/</guid><description>给出单体架构的维护策略，强调模块化与边界控制。</description></item><item><title>发布/订阅在可扩展性上的缺点：一致性与可观测性成本</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/publish-subscribe-cons/</link><pubDate>Sat, 24 Jan 2026 12:29:51 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/publish-subscribe-cons/</guid><description>分析发布/订阅模型在扩展性方面的缺点与工程成本。</description></item><item><title>如何避免供应商锁定（Vendor Lock-in）：策略与实践</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/vendor-lock-in/</link><pubDate>Sat, 24 Jan 2026 12:29:51 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/vendor-lock-in/</guid><description>给出防止供应商锁定的工程策略，包括抽象层、可迁移架构与数据可移植性。</description></item><item><title>如何设计高可扩展系统：从瓶颈到弹性</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-scalable-systems/</link><pubDate>Sat, 24 Jan 2026 12:29:51 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-scalable-systems/</guid><description>给出设计高可扩展系统的核心原则与实践步骤。</description></item><item><title>什么是三层架构：职责划分与工程价值</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/threelayer-architecture/</link><pubDate>Sat, 24 Jan 2026 12:29:51 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/threelayer-architecture/</guid><description>解释三层架构的分层职责、优缺点与适用场景。</description></item><item><title>C10k 问题怎么解决：高并发连接的策略</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/c10k-strategies/</link><pubDate>Sat, 24 Jan 2026 12:25:49 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/c10k-strategies/</guid><description>解释 C10k 的成因与解决策略，包括事件驱动、内核调优与连接管理。</description></item><item><title>横向扩展 vs 纵向扩展：区别、场景与取舍</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/scale-up-vs-scale-out/</link><pubDate>Sat, 24 Jan 2026 12:25:49 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/scale-up-vs-scale-out/</guid><description>解释 scale up 与 scale out 的差异、适用场景与成本模型。</description></item><item><title>什么是 CQRS：命令与查询职责分离</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cqrs-basics/</link><pubDate>Sat, 24 Jan 2026 12:25:49 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cqrs-basics/</guid><description>解释 CQRS 的核心思想、适用场景与落地成本。</description></item><item><title>性能与可扩展性的关系：别把快当成能扩</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-vs-scalability/</link><pubDate>Sat, 24 Jan 2026 12:25:49 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-vs-scalability/</guid><description>解释性能与可扩展性的差异与关系，并给出架构决策与指标建议。</description></item><item><title>缓存什么时候危险：一致性、失效与业务风险</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/caching-when-dangerous/</link><pubDate>Sat, 24 Jan 2026 12:23:30 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/caching-when-dangerous/</guid><description>说明缓存何时会带来风险，并给出适用条件与规避策略。</description></item><item><title>Web 与桌面应用的容错管理差异：思路与实践</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/fault-tolerance-web-vs-desktop/</link><pubDate>Sat, 24 Jan 2026 11:20:31 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/fault-tolerance-web-vs-desktop/</guid><description>对比 Web 与桌面应用的容错管理差异，给出关键策略与实践指南。</description></item></channel></rss>