TCP vs UDP

Choosing the Right Tool

TCP and UDP are both Transport Layer protocols, but they serve fundamentally different purposes. The choice between them isn't about which is "better" — it's about which is right for the job.

Side-by-Side Comparison

  Feature            │ TCP                    │ UDP
  ───────────────────┼────────────────────────┼────────────────────────
  Connection         │ Connection-oriented    │ Connectionless
  Reliability        │ Guaranteed delivery    │ Best-effort (no guarantee)
  Ordering           │ Ordered                │ No ordering
  Speed              │ Slower (overhead)      │ Faster (minimal overhead)
  Header size        │ 20-60 bytes            │ 8 bytes
  Flow control       │ Yes (window size)      │ No
  Congestion control │ Yes                    │ No
  Error checking     │ Checksum + ACKs        │ Checksum only
  Retransmission     │ Yes                    │ No
  Broadcast/Multicast│ No                     │ Yes

Use Cases

  Use TCP when:                     Use UDP when:
  ─────────────────────────         ─────────────────────────
  ✓ Data must arrive complete      ✓ Speed is critical
  ✓ Order matters                  ✓ Some data loss is acceptable
  ✓ You need confirmation          ✓ Real-time delivery needed
  ✓ No tolerance for errors        ✓ Simple request/response

  Examples:                         Examples:
  • Web browsing (HTTP/HTTPS)      • Video streaming
  • Email (SMTP, POP3, IMAP)       • Online gaming
  • File transfer (FTP, SCP)       • DNS queries
  • Database connections           • Voice/Video calls (VoIP)
  • Remote login (SSH, Telnet)     • IoT sensor data

The Performance Trade-Off

TCP's reliability comes at a cost:

• Latency — The three-way handshake adds at least one round-trip time before data can be sent. UDP sends immediately.
• Overhead — TCP headers are 20-60 bytes. UDP headers are 8 bytes. For small messages, this overhead is significant.
• Retransmission delay — When a TCP segment is lost, the sender waits for a timeout before retransmitting. This can add hundreds of milliseconds of delay.
• Head-of-line blocking — In TCP, if one segment is lost, all subsequent segments must wait even if they arrived correctly. UDP has no such issue.

For real-time applications, these delays are unacceptable. A video call that buffers like a webpage would be unusable.

QUIC: The Best of Both Worlds?

QUIC is a newer transport protocol developed by Google and now used in HTTP/3. It runs over UDP but adds TCP-like reliability features — connection establishment, ordering, and retransmission — while avoiding TCP's limitations.

QUIC establishes connections faster (0-RTT or 1-RTT vs. TCP's 3-RTT), handles packet loss better (no head-of-line blocking), and includes built-in encryption. It's an example of how UDP is becoming the foundation for next-generation protocols.