RollupDB Adds SQL, Scheduled Rollups and Streams You Can Change Later

Sat, 17 Oct 2026 00:00:00 +0000

RollupDB went from 0.1.1 to 0.4.1 on its launch day. Versions 0.2 to 0.4 added one feature each. The point of all three was day thirty, not day one. The release post has the details.

0.2.0 stops relying on someone to remember advance. The HTTP service now rolls every stream up once a minute, and the Go library has the same schedule for embedders. 0.3.0 lets a stream take a new version when its retention or grace period turns out to be wrong, or when it should start keeping percentiles. What the stored buckets were built from stays fixed: dimensions, bucket widths, start time. A sketch added later covers buckets from then on, and older ranges say percentiles weren’t kept rather than guessing.

RollupDB Launches, an Aggregate Database That Keeps Years of Statistics and Lets the Raw Events Go

Sat, 17 Oct 2026 00:00:00 +0000

RollupDB, the studio’s eleventh project, is an aggregate database in a single file. You declare up front which statistics you’ll want, and it keeps those for years while the raw readings go. Old buckets fold into coarser ones as they age: seconds into minutes, minutes into hours, hours into days. Version 0.1 came out on 17 October as one Go binary for Linux, macOS and Windows, with a Go library and a small loopback HTTP service on the same engine. The same day, 0.1.1 followed: it refuses a clock that jumps far ahead unless you lift the limit, and gives HTTP snapshots more time. The code is open source under Apache 2.0.

RollupDB on SoftDevStudio.com

RollupDB Adds SQL, Scheduled Rollups and Streams You Can Change Later

RollupDB Launches, an Aggregate Database That Keeps Years of Statistics and Lets the Raw Events Go