<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tcc on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/tcc/</link>
    <description>Recent content in Tcc on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/tcc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Distributed Transaction Solutions — Seata vs CAP vs HMily</title>
      <link>https://www.pistack.xyz/posts/2026-05-18-self-hosted-distributed-transactions-seata-cap-hmily-guide/</link>
      <pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-18-self-hosted-distributed-transactions-seata-cap-hmily-guide/</guid>
      <description>&lt;p&gt;When microservices span multiple databases and systems, ensuring data consistency across service boundaries becomes one of the hardest problems in distributed computing. Traditional ACID transactions do not work across service boundaries, forcing teams to choose between eventual consistency patterns and distributed transaction coordinators.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
