Now that you know how data moves between players and servers, it's time to decide how the server itself should be organized. Game server architecture is about who owns the truth, how often state is sent, and how many matches a single machine or cluster can safely run at once.
This module covers the ideas you'll meet again and again: the authoritative server that keeps cheaters out, state synchronization and rollback techniques that hide latency, replication in a real engine like Unreal, and orchestration tools such as Agones that start, scale, and retire dedicated game servers on demand.
Don't worry about memorizing every pattern. Focus on understanding the trade-offs, such as responsiveness versus fairness and simplicity versus scale. They'll guide your choices in Real-Time Communication, the next module.
A look at rollback networking in a shipped fighting game, a useful contrast to the authoritative-server model most action games use.
How replication and network performance are handled in Unreal Engine, and what that means for the load on your game server.
An introduction to Agones, the open-source project for hosting, running, and scaling dedicated game servers on Kubernetes.