<?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 RollupDB.com</title>
    <link>https://rollupdb.com/tags/explainer/</link>
    <description>Recent content in Explainer on RollupDB.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rollupdb.com/tags/explainer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What an Aggregate Database Keeps When the Raw Events Are Gone</title>
      <link>https://rollupdb.com/what-an-aggregate-database-keeps-when-the-raw-events-are-gone/</link>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/what-an-aggregate-database-keeps-when-the-raw-events-are-gone/</guid>
      <description>&lt;p&gt;Most databases keep what you put in. An aggregate database doesn&amp;rsquo;t. It keeps what you&amp;rsquo;ll ask about later, and only that. You tell it up front: for this stream of latencies, I want the count, the sum, the min and max, the mean, the variance and the 99th percentile, grouped by service. Then it&amp;rsquo;s free to throw the individual readings away, because it already has what those readings were going to be used for.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
