<?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 文叨叨 | IaaS 排障手记</title><link>/tags/%E5%9B%9E%E6%BB%9A/</link><description>Recent content in 回滚 on 文叨叨 | IaaS 排障手记</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Sun, 26 Apr 2026 10:00:00 +0800</lastBuildDate><atom:link href="/tags/%E5%9B%9E%E6%BB%9A/index.xml" rel="self" type="application/rss+xml"/><item><title>正向流程容易，逆向回滚才是灾难</title><link>/posts/forward-easy-rollback-hard/</link><pubDate>Sun, 26 Apr 2026 10:00:00 +0800</pubDate><guid>/posts/forward-easy-rollback-hard/</guid><description>当流程跨越了多个服务，一旦中途某一步失败，如何把已经扭转的状态干净地恢复原状，是软件架构里最重的活。优秀的架构师会尽量避免物理回滚，把流程设计为只能向前。</description></item></channel></rss>