How one person keeps every used car in Cyprus live in one search
AllCars looks like a slick app and a tidy weekly report. Behind it is a deliberately boring stack the kind that doesn't break on a Sunday morning. Here's the gist.
If you've used AllCars to search used cars in Cyprus, you've probably noticed it just works. Listings are fresh. The deal score loads instantly. Saved searches actually fire. The reason isn't a clever piece of architecture. It's that I picked a small set of well-understood tools and refused to add anything I didn't have to.
One small server, a lot of moving pieces
Everything runs on a single, modest cloud server. That sounds underpowered until you realise that for a country the size of Cyprus, the entire used-car market fits comfortably in memory. There's no need for a fleet. Just a tidy single host with good uptime habits. Result: latency is short, the bill is small, and there's nowhere for a request to get lost.
The work is split into small, single-purpose services. One job ingests new listings. One scores them. One serves the API your phone talks to. One handles the saved-search alerts. Each one does roughly one thing, restarts cleanly, and can be replaced without taking the rest down.
Boring on purpose
No exotic databases. No managed-everything pipeline. Auto-renewing TLS so the padlock just works. A continuous integration step that refuses to ship if tests are red. Backups that are tested as well as taken. None of it would impress at a conference. All of it stops the platform from waking me up at 3am.
For Cyprus drivers, the impact is the part you don't notice. The page loads. The listing's there. The price history is there. The notification arrives a couple of minutes after a new match appears. That's the whole job, and the boring stack is what gets it done consistently.
See it for yourself
Every public used-car listing in Cyprus, in one search. Fast, fresh, and quiet.
Open AllCarsHow I make sure the index is actually doing what it says.