Every multiplayer game is really a conversation between clients and a server, and your server-side code lives or dies by how well that conversation is carried out. Networking fundamentals give you the vocabulary and mental models to decide how player input, game state, and chat messages should travel across the internet.
This module focuses on the transport choices that matter most for games: TCP for ordered, reliable delivery, UDP for fast, loss-tolerant updates, and WebSockets for persistent two-way connections in browser and lobby-style games. You'll see why a late packet can be worse than a lost one, and how real studios build responsive netcode on top of these protocols.
You don't need to master every layer of the stack. Aim to leave knowing when to reach for TCP, UDP, or WebSockets, because that choice shapes everything in Game Server Architecture, the next module.
The core differences between TCP and UDP, their pros and cons, and demo code that shows how each one behaves in practice.
Why real-time games often prefer UDP: what happens when data is lost or delayed, and how a fresh update can beat a retransmitted one.
How WebSockets keep a persistent two-way connection open between client and server, and a simple example of building one.
A GDC talk on how a shipped multiplayer shooter uses a server-authoritative model with client-side prediction to stay responsive.