Night shift · Client work

The fleet sync

A platform that pulls each trucking company's data out of the systems on its trucks and into one place its people can actually use.

A toy version, with the detail sanded off. The blocks are made up and the counts come from the toy.

01
Providers
Tracking boxes and shop systems on every truck keep producing records, whether anyone is listening or not.
02
Worker
One small worker is the only thing that talks to them. It visits each in turn and takes a few at a time, so nobody's rate limit is hit.
03
Database
Everything lands in one database. It is the single thing the whole product leans on, by choice.
04
Walls
Each company's rows sit behind their own wall, enforced by the database itself and not by the app remembering to check.
05
Nap
If the database goes down, the worker waits. The providers keep their history, and it catches up from where it stopped.
06
New fleet
A new connection is picked up on the worker's next pass. Nothing is restarted.

Why it is built this way

The database is also the queue. No extra queue system until there is a problem only one can solve.
Only the worker talks to providers, so there is one place to slow down, retry or fix.
Access is checked twice: once by the page, once by the database.
Writing back to a provider is off unless someone switches it on for that company.

This is the one I build with my brother and friends, and I am happy it runs on real data from a first customer and not on samples.

I love building the analytics and looking after it, and I want to understand the industry better.

I am hoping for more real customers soon, so there is more to explore.

Tea