Engineer Atlas
OverviewLearnJourneysPacket LabDebuggerRoadmapPracticeInterviewCheat Sheet
OverviewLearnJourneysPacket LabDebuggerRoadmapPracticeInterviewCheat SheetCompareConnections
Computer Networking
  • How the Internet Works
  • Ethernet, MAC & the Link Layer
  • IP, IPv4, IPv6, Subnets, NAT & Ports
  • Routing
  • DNS
  • UDP
  • TCP
  • TLS & Certificates
  • HTTP/1.1, HTTP/2 & HTTP/3
  • WebSockets, SSE & Polling
  • Proxies, Load Balancers & CDNs
  • Firewalls & VPNs
  • Container & Kubernetes Networking
  • Network Performance
  • Network Debugging & Capstone
  • Packet Lab
OS + Networking
  • OS + Networking Together
Networking/Learn/UDP
Computer Networking

UDP

Datagrams over IP with no connection, no ordering and no retransmission — and why DNS, real-time media and QUIC choose exactly that.

The question this module answers · Why would anyone want a transport that can lose your data?
UDP: Datagrams and the Contract You Choose
▶ interactive

UDP wraps an application message in an 8-byte header and hands it to IP as one datagram — no connection, no ordering, no retransmission, no flow or congestion control — so the application gets message boundaries, minimal latency and total control, and inherits every responsibility TCP would otherwise have taken.

Engineer Atlas
GitHub·LinkedIn