Roadmap on Precomputing.com

Introduction

Fri, 25 Sep 2026 00:00:00 +0000

Answers ready before you ask: one small language keeps counts, percentiles, candles, invoices and log dashboards current in a SQLite file as the data arrives.

Precomputing is a project to make answers cheap. A short policy names the streams of events you have and the answers you want ready, and says how long each level of detail should live. From then on every event updates those answers the moment it arrives, so a question becomes a lookup, and old detail fades on the schedule you set.

How It Works

Fri, 25 Sep 2026 00:00:00 +0000

The idea. Decide the questions first. Keep their answers current as each event arrives, in one SQLite file, and let raw detail fade on a schedule while unusual events stay whole.

Before and After

Today a system that collects events usually keeps all of them and computes each answer when someone asks. A dashboard scans the last hour on every refresh. An invoice adds up a month of requests at the month’s end. Precomputing moves the work to the moment each event arrives:

Next Applications: Eight Places Where Answers Kept Ready Could Fit

Fri, 25 Sep 2026 00:00:00 +0000

The four case studies share one pattern. The questions are known in advance and the events arrive as a stream, so the answers can be kept current as each event lands, while raw detail stays only as long as it is useful. API monitoring, market data, usage billing and logs came first because the demos cover them.

The pattern turns up in many more places. None of the eight below has been tested, and none runs Precomputing today. This post sets out what each would ask of the platform, and which parts already carry over from the demos. It is a map for choosing pilots, ideally together with the people who run these systems.