01 / DATA & RELIABILITY
Founder’s workFrom daily manual recovery
to a pipeline you can trace.
Digging through logs and recovering by hand, every day.
Every time data collection stopped, a developer had to search the logs and run recovery commands. Error output was sparse, and maintenance was eating into time for new development.
Start with alerts, then change the structure.
Alerts came first. The serial processing was then rebuilt on a worker–dispatcher model that runs jobs through a queue. Tasks were given states such as waiting, running, succeeded and failed, and a recovery endpoint that is called automatically was added.
From one API to several applications.
The shared design was rolled out to applications for several APIs. Another department that needed the same API asked to use one of them, source code and all, and received the design, shared code and tooling.
WHAT CHANGED
A system that tracks state and recovers on its own. Data rarely has to be fetched again, and the design was left in a form others could reuse.