Problem context and objectives
Launch-day backend engineer · Neon Rift, a four-player real-time arena
Ship the first global multiplayer match without lag, cheating, or lost results.
Two hundred and fifty thousand players arrive tonight. If clients disagree about one hit, the match feels unfair; if a session dies, players must recover without replaying the whole battle.
How you win
- 1Every match has one authoritative source of truth
- 2Player input reaches the regional session within the latency budget
- 3A dropped player can reconnect from a recent snapshot
- 4Final results are stored exactly once
Rules and pressure
- 250K concurrent players
- Four players per match
- Input-to-state p95 below 100 ms
- Reconnect window: 10 seconds
New words in this mission
Open a term for a plain-language explanation.p95 latency+
If 100 actions are measured, about 95 finish within this time and the slowest 5 take longer. It exposes lag that an average can hide.
authoritative state+
The one trusted version of the game world. Players can suggest actions, but this source decides what officially happened.
tick rate+
How often the game simulation updates each second. At 20 ticks per second, the server advances the world every 50 milliseconds.
snapshot+
A saved checkpoint of current state. After a crash or reconnect, the system restores this checkpoint instead of rebuilding everything from the beginning.
latency+
The waiting time from starting an action until its result is available. Lower latency makes interactions feel more immediate.
Live architecture trace
Launch a Multiplayer Arena: request to outcome
Player device sends “input command” to Realtime gateway. An authoritative session is the anti-cheat and consistency boundary. Clients send intent; the session validates, orders, and applies it to one official state.
You are launching a real-time four-player arena game. Design the path from a player's button press to an authoritative match update, then make reconnects and match results reliable. Follow one real user action through the complete architecture; a component is useful only when you can explain the request, state, or failure it handles.