🎮 Gaming · Deployment · Pro
Global Game Server Deployment
How an online game runs servers close to players worldwide: regional fleets, a global matchmaker, and central account and store services.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
What this diagram shows
- Game servers run in several regions to keep latency low
- A global matchmaker picks the best region for each match
- Accounts, inventory and store stay central
Prompt used
Deployment for a global multiplayer game: players connect to a global API for login and matchmaking; regional fleets of dedicated game servers (Agones on Kubernetes) run in Mumbai, Singapore, Frankfurt and Virginia; the matchmaker measures player ping to each region and allocates a server there. Central services (accounts, inventory, store, leaderboards) run in one primary region with a replicated database; telemetry streams to an analytics pipeline.
Mermaid code
flowchart TB
P[Players worldwide] --> API[Global API - login, matchmaking]
API --> MM[Matchmaker - ping-based region choice]
subgraph Regions[Regional game server fleets - Agones]
R1[Mumbai fleet]
R2[Singapore fleet]
R3[Frankfurt fleet]
R4[Virginia fleet]
end
MM --> R1
MM --> R2
MM --> R3
MM --> R4
P -->|UDP gameplay| R1
subgraph Central[Primary region]
ACC[Accounts]
INV[Inventory and Store]
LB[Leaderboards]
DB[(Replicated DB)]
end
API --> ACC
API --> INV
R1 -->|Results| LB
ACC --> DB
INV --> DB
R1 -.telemetry.-> AN[Analytics Pipeline]Related templates
Multiplayer Game Backend Architecture
The backend for an online multiplayer game: player accounts, matchmaking, dedicated game servers, leaderboards and in-game purchases.
Game Matchmaking Sequence
How a player gets into a match: joining the queue, skill-based matching, server allocation and connecting to the game server.
Multiplayer Game Session States
The states of an online match on a game server: lobby, loading, in progress, pauses, reconnects and results.
Game Leaderboard Data Pipeline
How match results turn into leaderboards and rankings: result events, anti-cheat checks, rating updates and cached leaderboards.
In-App Purchase Flow
How an in-game purchase is completed safely: store purchase, receipt validation on the server, granting items and handling refunds.
Game Player and Inventory Schema
Tables for an online game: players, characters, items, inventories, currencies, purchases and match history.