Post
When a million players log in at once, load balancing decides which servers handle whom so nothing catches fire.
Load balancing in games distributes player connections and computational work across multiple servers to prevent any single server from being overwhelmed. For matchmaking, it means routing players to servers with available capacity in their geographic region. For MMOs, it means sharding the world across multiple servers or using dynamic instancing to spin up new copies of crowded areas. For game backends, it means distributing authentication, leaderboard, and inventory requests across server clusters. The strategies range from simple round-robin assignment to sophisticated algorithms that consider server load, player latency, geographic proximity, and game state complexity. Auto-scaling -- spinning up new server instances when demand spikes and shutting them down when it drops -- keeps costs proportional to actual usage.
Example
World of Warcraft uses a combination of realm sharding and dynamic phasing to load balance its population. When a new expansion launches and millions of players converge on the same starting zone, the server dynamically creates multiple instances of that zone and distributes players across them, preventing the crushing lag that plagued earlier launches.
Why it matters
Every multiplayer game eventually faces the scaling problem. A game that cannot handle its own success -- crashing on launch day, lagging during peak hours, timing out during events -- loses players who may never come back. Load balancing is the infrastructure that turns a good game into one that can actually survive contact with its audience.
Related concepts