How a game backend models progression: score submissions, leaderboards scoped global or regional or friends across daily and seasonal periods, rank derived rather than stored, multi-step achievements with progress, unlock rewards and anti-cheat flags.
How a competitive game backend matches players: skill ratings with uncertainty and full rating history, parties, regional queues, accept-or-decline proposals, server allocation, match rosters with backfill and abandonment penalties.
How a tournament platform models competition: single and double elimination, round robin and Swiss stages, teams with roster locks, a bracket stored as a node tree, best-of series with per-map results, venues and prize distribution.
How a game backend models virtual currency: hard and soft currencies, player wallets, an append-only double-entry ledger of every source and sink, a personalised item shop, validated store receipts, refunds and a battle pass.
How an online game models items: templates versus instances, stacking rules, affixes rolled per copy, bags and bank and equipped slots, soulbinding, durability, two-sided player trades, mail with attachments and an append-only item audit log.