Skip to content

Livesport

Nine internal systems behind a sports platform serving 100M+ people

Coordinate Sports data / high-traffic consumer software

Livesport's internal systems must stay correct under spiky load, because an error shows up as wrong scores for tens of millions of people within seconds.

What we did

We designed, built and operated nine internal systems for Livesport in TypeScript and Node.js, and built them so Livesport's own team can maintain them.

TypeScript / Node.js · High-throughput services · Data-oriented systems

Result

Nine internal systems running in production behind a platform with more than 100 million users.

In production

Livesport runs one of the most-visited sports-results platforms in the world. When a match result changes, tens of millions of people see it within seconds. If an internal system behind it is slow or wrong, they see the wrong score.

What we built

Nine internal systems in TypeScript and Node.js. Each one works on plain data and stays small enough to reason about at peak traffic. That’s why Livesport’s own engineers can own and extend them after we handed them over.

Tell us about a decision like this one

Jiri or Ivo will tell you if it is worth building software for it.