<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Saga on 知识铺的博客</title>
    <link>https://index.zshipu.com/geek001/tags/Saga/</link>
    <description>Recent content in Saga on 知识铺的博客</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://index.zshipu.com/geek001/tags/Saga/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>事务性发件箱模式如何解决微服务双写一致性问题</title>
      <link>https://index.zshipu.com/geek001/post/20260904/%E4%BA%8B%E5%8A%A1%E6%80%A7%E5%8F%91%E4%BB%B6%E7%AE%B1%E6%A8%A1%E5%BC%8F%E5%A6%82%E4%BD%95%E8%A7%A3%E5%86%B3%E5%BE%AE%E6%9C%8D%E5%8A%A1%E5%8F%8C%E5%86%99%E4%B8%80%E8%87%B4%E6%80%A7%E9%97%AE%E9%A2%98/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://index.zshipu.com/geek001/post/20260904/%E4%BA%8B%E5%8A%A1%E6%80%A7%E5%8F%91%E4%BB%B6%E7%AE%B1%E6%A8%A1%E5%BC%8F%E5%A6%82%E4%BD%95%E8%A7%A3%E5%86%B3%E5%BE%AE%E6%9C%8D%E5%8A%A1%E5%8F%8C%E5%86%99%E4%B8%80%E8%87%B4%E6%80%A7%E9%97%AE%E9%A2%98/</guid>
      <description>微服务中更新数据库后立即发布事件到消息代理的做法，一旦网络失败就会让已提交的事件永久丢失；若事件先发成功而数据库回滚，下游又会收到幻影事件。事务性发件箱模式要求把事件存入数据库的发件箱表，与业务数据在同一事务内提交，然后由独立进程负责转发到 RabbitMQ 或 Kafka。 这种双写漏洞在实际生产环</description>
    </item>
  </channel>
</rss>
