Use Cases on RollupDB.com

Keeping Years of Cold Room Temperatures on an IoT Gateway With RollupDB

Sun, 18 Oct 2026 00:00:00 +0000

Picture a food distributor with six cold rooms, each with a sensor that reports the temperature every second. The readings go to a small gateway in the building. Somebody will want two things from that data. Today: is any room warming up? Two years from now, during an audit or an insurance claim: what were the temperatures in room 4 last March, and how bad did it get?

Raw readings don’t fit that brief. Six sensors at one reading a second come to about 190 million readings a year, and nobody wants to keep that on a gateway or ship it all to the cloud just to answer a question once a year. What the audit needs is the coldest, the warmest, the average and the spread for each room, hour by hour. That’s what RollupDB keeps.

Tracking AI Model Cost and Token Use per Feature With RollupDB

Sun, 18 Oct 2026 00:00:00 +0000

An app calls two language models, a large one and a small one, from three features: a support chat, document summaries and search. Every call has a token count and a price. Finance wants the monthly bill split by feature. Engineering wants to know which feature sends the longest prompts, and whether moving support chat to the small model last quarter actually saved money.

The provider’s dashboard shows the bill, not your features. Logging every call answers everything, and in a year it’s millions of rows, most holding prompt text you’d rather not keep at all. What the questions need is sums and counts per model and feature over time, plus the shape of the token counts. RollupDB keeps that and lets the calls go.

Tracking API Latency and Errors per Endpoint for a Year With RollupDB

Sun, 18 Oct 2026 00:00:00 +0000

A small online shop runs one API with four endpoints that matter: product pages, the cart, search and checkout. The team wants a dashboard for today. They also want to answer, next spring, whether checkout got slower after the autumn release, and whether its p99 last Black Friday was worse than this one.

Request logs answer that, if you keep them. Most teams don’t keep them for a year because the bill for storing and scanning them grows every month. Monitoring tools keep the history, usually as pre-averaged numbers, and a p99 averaged across minutes isn’t the hour’s p99. RollupDB sits in between. It keeps per-endpoint counts, sums, extremes and a percentile sketch, and merges them correctly as they age.