Real-Time Gaming Leaderboard System Design — Visual Journey

What You Should Understand Now

• A leaderboard ranks verified outcomes, not raw gameplay — a client-supplied score is never trusted directly; only an authenticated game server (or equivalent verification) can move a rank.
• Equal scores alone never define a unique order — FlowRank uses a deterministic tie-break (earlier achievement timestamp, then stable player ID) so the displayed ranking never flips arbitrarily.
• Redis sorted sets are an excellent baseline for bounded leaderboards, not an automatic answer to every scale problem — ZADD/ZREVRANK/ZREVRANGE have real complexity characteristics, memory costs, and hot-key limits.
• A durable, ordered event log — not the live Redis structure — is the actual source of truth; the ranking index is a materialized, eventually-consistent projection of it, with a bounded staleness contract.
• A friends-only leaderboard cannot be produced by filtering a global top-100 — it requires fetching the small eligible friend set directly and sorting only that subset.
• Splitting one massive board across shards breaks simple exact ZREVRANK — a shard-local rank is not a global rank, and exact global rank at extreme scale needs either a specialized structure or an accepted approximation.

Concepts in This Visual

Go Deeper