Networking for Server Side Game Developers
Networking for games is how data moves between players and servers. TCP guarantees ordered delivery, UDP trades reliability for lower latency, and WebSockets suit browser clients. Latency, jitter and bandwidth limit what is possible, so game protocols often add their own reliability, compression and prioritisation on top of UDP.
Stage: Foundations · Part of the Server Side Game Developer roadmap · Last reviewed 19 November 2026
What to learn in Networking
- Choose TCP, UDP or WebSockets for a given game genre
- Explain head-of-line blocking and why it hurts realtime games
- Measure round-trip time and jitter between two machines
- Design a compact binary message format for position updates
- Add sequence numbers and acknowledgements on top of UDP
- Estimate bandwidth per player at a given tick rate
Networking interview questions
Why do many fast-paced games use UDP instead of TCP?
TCP retransmits lost packets and delivers in order, so one lost packet delays everything behind it. In a game, old position data is useless anyway, so UDP lets newer state arrive without waiting, with reliability added only for messages that need it.
What is the difference between latency and jitter?
Latency is the time a packet takes to travel, usually quoted as round trip. Jitter is the variation in that time between packets. High jitter makes motion look uneven, so clients use interpolation buffers to smooth it.
Where Networking fits in the Server Side Game Developer roadmap
Networking belongs to the Foundations stage (beginner level), which takes about 6 hours. Language, networking and game concepts.
Other units in this stage
Back to the full Server Side Game Developer roadmap