We replaced Redis's arbitrary equal-score ordering with first-arrival wins, then measured the latency and memory bill instead of calling it free.
Engineering posts often end with:
The new design is correct, scalable, and fast.
Fast compared with what?
When we changed Podium so tied players
rank by arrival time instead of player ID, we added:
Redis sorted sets make leaderboards easy, until two players have the same score. Here is how we made ties fair, deterministic,…
The Problem We Were Actually Solving We ran an in-memory leaderboard service for a competitive event...
I want to be upfront about something: I didn't build this. Our engineering team did. But I get to...
My serverless benchmark prints 0.88 vs 0.3025 — real measurements running on editorial weights. Every index has a committee; the…
Hash tags make atomic leaderboard updates work in Redis Cluster, but they do not split one leaderboard across nodes. Here is the…
Every benchmark on this site compares my own ESLint plugins to competitors — a real conflict of interest, not a disclaimer I can…
