Infrastructure for Server Side Game Developers
Infrastructure is where game servers run. Containers package them, Kubernetes schedules them, and Agones extends Kubernetes with game server fleets, allocation and lifecycle states. Load testing and capacity planning estimate how many servers and what hardware are needed before launch or a big event.
Stage: Scale and Operations · Part of the Server Side Game Developer roadmap · Last reviewed 19 November 2026
What to learn in Infrastructure
- Containerise a game server with a small Dockerfile
- Explain how Agones allocates a ready game server to a match
- Define a Fleet and autoscale it with a FleetAutoscaler
- Write a bot-based load test that simulates many players
- Estimate players per server from CPU and memory use
- Plan spare capacity for launch spikes
Infrastructure interview questions
Why is plain Kubernetes not enough for game servers?
Game servers are stateful, long-lived sessions that must not be killed mid-match, and each needs its own address and port. Agones adds fleet management, allocation and shutdown states designed for that, while standard deployments assume interchangeable stateless pods.
How do you capacity plan for a game launch?
Measure how many concurrent players one server holds under load tests, forecast peak concurrency from pre-registrations and marketing, add headroom, and check that databases, matchmaking and network limits scale too. Rehearse with load tests.
Where Infrastructure fits in the Server Side Game Developer roadmap
Infrastructure belongs to the Scale and Operations stage (intermediate level), which takes about 6 hours. Live service reality.
Other units in this stage
Back to the full Server Side Game Developer roadmap