<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Explainer on XKV.org</title>
    <link>https://xkv.org/tags/explainer/</link>
    <description>Recent content in Explainer on XKV.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://xkv.org/tags/explainer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What an Explainable Key-Value Store Is and Why Small Values Need One</title>
      <link>https://xkv.org/what-an-explainable-key-value-store-is-and-why-small-values-need-one/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://xkv.org/what-an-explainable-key-value-store-is-and-why-small-values-need-one/</guid>
      <description>&lt;p&gt;The values that cause the most trouble are small. A credit limit. A timeout. A price. A flag that switches a feature on for ten percent of users. Each one fits in a few bytes, and each one can stop a business for an afternoon when it changes and nobody knows why.&lt;/p&gt;&#xA;&lt;p&gt;Every key-value store keeps the value. Some keep old values too. What none of them keep is the reason, and above all the link from one change to the change that caused it. That link is what people ask about. Support can already see the customer&amp;rsquo;s limit. What they need is why it&amp;rsquo;s 50 when it was 100 yesterday.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
