<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Open Source on RollupDB.com</title>
    <link>https://rollupdb.com/tags/open-source/</link>
    <description>Recent content in Open Source 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/open-source/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RollupDB Launches as an Open Source Database for Years of Statistics</title>
      <link>https://rollupdb.com/rollupdb-launches-as-an-open-source-database-for-years-of-statistics/</link>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/rollupdb-launches-as-an-open-source-database-for-years-of-statistics/</guid>
      <description>&lt;p&gt;RollupDB 0.1 is out, under the Apache License 2.0. It&amp;rsquo;s an aggregate database in one file: you tell it which statistics matter, and it keeps those for years while it lets the raw events go. Seconds fold into minutes, minutes into hours, hours into days. A query a year later still gets the right count, the right extremes and a percentile with a stated error.&lt;/p&gt;&#xA;&lt;p&gt;The pitch is simple, and the numbers are what make it worth trying. In the recorded test, five years of readings from two services, 2.8 million of them, took 207 MB as raw JSON lines. The RollupDB file holding all of it was 15.4 MB, with seconds for the last day, minutes for the last day, hours for the last week and a bucket per day going back the full five years.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
