<?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/%E5%8F%AF%E9%9D%A0%E6%80%A7/</link><description>Recent content in 可靠性 on Jeanphilo Blog</description><generator>Hugo -- 0.159.2</generator><language>zh-cn</language><lastBuildDate>Sat, 24 Jan 2026 15:42:47 +0800</lastBuildDate><atom:link href="https://shio-chan-dev.github.io/jeanblog/zh/tags/%E5%8F%AF%E9%9D%A0%E6%80%A7/index.xml" rel="self" type="application/rss+xml"/><item><title>为什么函数式编程越来越受关注</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/language/why-fp-popular-now/</link><pubDate>Sat, 24 Jan 2026 15:42:47 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/language/why-fp-popular-now/</guid><description>从并发、可靠性与工程规模角度解释函数式编程的流行原因。</description></item><item><title>除了攻击之外，哪些设计会导致拒绝服务</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-issues-causing-dos/</link><pubDate>Sat, 24 Jan 2026 13:27:25 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-issues-causing-dos/</guid><description>讨论架构设计缺陷如何引发类似 DoS 的系统故障。</description></item><item><title>分布式计算的八大谬论：你真的能相信网络吗？</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/fallacies-of-distributed-computing/</link><pubDate>Sat, 24 Jan 2026 13:08:42 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/fallacies-of-distributed-computing/</guid><description>用工程视角解释分布式计算的常见谬论与风险。</description></item><item><title>分布式系统如何处理故障：超时、重试与降级</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/failure-handling/</link><pubDate>Sat, 24 Jan 2026 13:08:42 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/failure-handling/</guid><description>总结分布式系统常见故障处理策略，并给出工程落地建议。</description></item><item><title>如何测试分布式系统：故障注入与一致性验证</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/distributed-testing/</link><pubDate>Sat, 24 Jan 2026 12:23:30 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/distributed-testing/</guid><description>从故障注入、时钟偏移、网络分区出发，给出分布式系统测试的工程方法。</description></item><item><title>远程过程调用（RPC）的通用缺点：成本与风险</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/rpc-common-drawbacks/</link><pubDate>Sat, 24 Jan 2026 12:23:30 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/rpc-common-drawbacks/</guid><description>总结 RPC 的通用缺点，包括耦合、可观测性与错误处理复杂度。</description></item><item><title>什么是 ACID：事务的四个核心属性</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/database/acid-basics/</link><pubDate>Sat, 24 Jan 2026 11:28:00 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/database/acid-basics/</guid><description>解释 ACID 的四个属性及其工程意义，并给出常见误区与实践建议。</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><item><title>什么时候使用异步通信：场景、收益与代价</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/async-communication-when/</link><pubDate>Sat, 24 Jan 2026 11:20:31 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/async-communication-when/</guid><description>解释同步/异步通信的取舍，并给出适用场景与落地建议。</description></item><item><title>为什么并发测试很难：非确定性与时序爆炸</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/concurrency/testing-concurrency-is-hard/</link><pubDate>Sat, 24 Jan 2026 11:11:28 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/concurrency/testing-concurrency-is-hard/</guid><description>从非确定性、时序组合爆炸与可复现性角度解释并发测试的难点，并给出缓解策略。</description></item></channel></rss>