<?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>ACID on Answer</title>
    <link>https://answer.freetools.me/tags/acid/</link>
    <description>Recent content in ACID on Answer</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>zh-cn</language>
    <lastBuildDate>Sat, 07 Mar 2026 08:04:40 +0800</lastBuildDate>
    <atom:link href="https://answer.freetools.me/tags/acid/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SQLite为何能征服世界：从三位开发者的固执到一万亿数据库实例的技术传奇</title>
      <link>https://answer.freetools.me/sqlite%E4%B8%BA%E4%BD%95%E8%83%BD%E5%BE%81%E6%9C%8D%E4%B8%96%E7%95%8C%E4%BB%8E%E4%B8%89%E4%BD%8D%E5%BC%80%E5%8F%91%E8%80%85%E7%9A%84%E5%9B%BA%E6%89%A7%E5%88%B0%E4%B8%80%E4%B8%87%E4%BA%BF%E6%95%B0%E6%8D%AE%E5%BA%93%E5%AE%9E%E4%BE%8B%E7%9A%84%E6%8A%80%E6%9C%AF%E4%BC%A0%E5%A5%87/</link>
      <pubDate>Sat, 07 Mar 2026 08:04:40 +0800</pubDate>
      <guid>https://answer.freetools.me/sqlite%E4%B8%BA%E4%BD%95%E8%83%BD%E5%BE%81%E6%9C%8D%E4%B8%96%E7%95%8C%E4%BB%8E%E4%B8%89%E4%BD%8D%E5%BC%80%E5%8F%91%E8%80%85%E7%9A%84%E5%9B%BA%E6%89%A7%E5%88%B0%E4%B8%80%E4%B8%87%E4%BA%BF%E6%95%B0%E6%8D%AE%E5%BA%93%E5%AE%9E%E4%BE%8B%E7%9A%84%E6%8A%80%E6%9C%AF%E4%BC%A0%E5%A5%87/</guid>
      <description>深入解析SQLite成为全球最广泛部署数据库的技术密码：从155.8KSLOC核心代码与92053KSLOC测试代码的极致质量比，到字节码虚拟机架构的优雅设计，从WAL模式的并发突破到原子提交的硬件级防御。揭示这个小团队如何用二十年时间打造出运行在每台智能手机、浏览器和飞机上的数据库引擎，以及它的设计边界与适用场景。</description>
    </item>
    <item>
      <title>数据库已提交的事务为何会丢失？从fsync到异步提交的持久性权衡</title>
      <link>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E5%B7%B2%E6%8F%90%E4%BA%A4%E7%9A%84%E4%BA%8B%E5%8A%A1%E4%B8%BA%E4%BD%95%E4%BC%9A%E4%B8%A2%E5%A4%B1%E4%BB%8Efsync%E5%88%B0%E5%BC%82%E6%AD%A5%E6%8F%90%E4%BA%A4%E7%9A%84%E6%8C%81%E4%B9%85%E6%80%A7%E6%9D%83%E8%A1%A1/</link>
      <pubDate>Sat, 07 Mar 2026 07:20:09 +0800</pubDate>
      <guid>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E5%B7%B2%E6%8F%90%E4%BA%A4%E7%9A%84%E4%BA%8B%E5%8A%A1%E4%B8%BA%E4%BD%95%E4%BC%9A%E4%B8%A2%E5%A4%B1%E4%BB%8Efsync%E5%88%B0%E5%BC%82%E6%AD%A5%E6%8F%90%E4%BA%A4%E7%9A%84%E6%8C%81%E4%B9%85%E6%80%A7%E6%9D%83%E8%A1%A1/</guid>
      <description>深入解析数据库持久性的技术本质。从事务提交后数据丢失的困惑出发，剖析fsync性能瓶颈、操作系统页面缓存、SSD写入缓存三层缓冲机制；详解MySQL innodb_flush_log_at_trx_commit、PostgreSQL synchronous_commit、Redis appendfsync、MongoDB write concern等配置的实际含义；分析group commit优化与SSD电源故障保护(PLP)的关键作用；提供不同场景下的持久性配置决策框架。</description>
    </item>
    <item>
      <title>分布式事务为何成了架构师的噩梦——从两阶段提交到Saga模式的技术权衡</title>
      <link>https://answer.freetools.me/%E5%88%86%E5%B8%83%E5%BC%8F%E4%BA%8B%E5%8A%A1%E4%B8%BA%E4%BD%95%E6%88%90%E4%BA%86%E6%9E%B6%E6%9E%84%E5%B8%88%E7%9A%84%E5%99%A9%E6%A2%A6%E4%BB%8E%E4%B8%A4%E9%98%B6%E6%AE%B5%E6%8F%90%E4%BA%A4%E5%88%B0saga%E6%A8%A1%E5%BC%8F%E7%9A%84%E6%8A%80%E6%9C%AF%E6%9D%83%E8%A1%A1/</link>
      <pubDate>Fri, 06 Mar 2026 08:00:28 +0800</pubDate>
      <guid>https://answer.freetools.me/%E5%88%86%E5%B8%83%E5%BC%8F%E4%BA%8B%E5%8A%A1%E4%B8%BA%E4%BD%95%E6%88%90%E4%BA%86%E6%9E%B6%E6%9E%84%E5%B8%88%E7%9A%84%E5%99%A9%E6%A2%A6%E4%BB%8E%E4%B8%A4%E9%98%B6%E6%AE%B5%E6%8F%90%E4%BA%A4%E5%88%B0saga%E6%A8%A1%E5%BC%8F%E7%9A%84%E6%8A%80%E6%9C%AF%E6%9D%83%E8%A1%A1/</guid>
      <description>深入解析分布式事务的核心困境与技术演进。从Jim Gray在1978年提出两阶段提交协议，到Hector Garcia-Molina在1987年发表Saga论文，再到Google Spanner的TrueTime机制和CockroachDB的Parallel Commits协议，揭示分布式事务四十五年来在强一致性与可用性之间的艰难平衡。基于FLP不可能性定理、Paxos Commit算法、XA协议规范以及Seata框架的实现经验，系统梳理分布式事务从阻塞协议到补偿模式的完整技术路径。</description>
    </item>
    <item>
      <title>fsync()不是你想的那样：数据库持久化的致命误解</title>
      <link>https://answer.freetools.me/fsync%E4%B8%8D%E6%98%AF%E4%BD%A0%E6%83%B3%E7%9A%84%E9%82%A3%E6%A0%B7%E6%95%B0%E6%8D%AE%E5%BA%93%E6%8C%81%E4%B9%85%E5%8C%96%E7%9A%84%E8%87%B4%E5%91%BD%E8%AF%AF%E8%A7%A3/</link>
      <pubDate>Fri, 06 Mar 2026 04:46:52 +0800</pubDate>
      <guid>https://answer.freetools.me/fsync%E4%B8%8D%E6%98%AF%E4%BD%A0%E6%83%B3%E7%9A%84%E9%82%A3%E6%A0%B7%E6%95%B0%E6%8D%AE%E5%BA%93%E6%8C%81%E4%B9%85%E5%8C%96%E7%9A%84%E8%87%B4%E5%91%BD%E8%AF%AF%E8%A7%A3/</guid>
      <description>深入剖析fsync()系统调用的真实行为与陷阱。从2018年PostgreSQL的fsyncgate事件，到USENIX ATC 2020关于fsync失败恢复的学术研究，系统梳理Linux文件系统(ext4/XFS/Btrfs)在fsync失败后的复杂行为——页面被标记为干净、错误只报告一次、重试反而成功。揭示为什么&amp;#34;重试fsync&amp;#34;是错误策略，以及PostgreSQL、MySQL、SQLite等主流数据库的应对方案。</description>
    </item>
  </channel>
</rss>
