<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Transactions on KvSQL.com</title>
    <link>https://kvsql.com/tags/transactions/</link>
    <description>Recent content in Transactions on KvSQL.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://kvsql.com/tags/transactions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Case Study: A Checkout That Is Never Half Done, Tested With 1200 Power Cuts</title>
      <link>https://kvsql.com/case-study-a-checkout-that-is-never-half-done-tested-with-1200-power-cuts/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://kvsql.com/case-study-a-checkout-that-is-never-half-done-tested-with-1200-power-cuts/</guid>
      <description>&lt;p&gt;A checkout touches several things that must change together. The cart goes away, an order appears with its lines, and the stock goes down. If the power fails halfway, the worst outcomes are an order with the stock never taken, or a paid order with the cart still sitting there. With a key-value store for carts and an SQL database for orders, those are two systems and two commits, and somebody has to write the cleanup for the gap between them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
