TCP vs UDP: Reliable vs Fast Communication

In previous chapters we explored how data is broken into packets and routed across networks.

But another important question remains:

How do applications actually send and receive those packets?

When you load a website, stream a video, send a message, or join an online game, your device needs a way to communicate reliably with another program on a remote machine.

This responsibility belongs to the transport layer of networking.

Two protocols dominate this layer:

TCP (Transmission Control Protocol)
UDP (User Datagram Protocol)

Both protocols move data between applications across the internet, but they take very different approaches.

Understanding the difference between TCP and UDP will help you understand why some internet activities prioritize reliability while others prioritize speed.

The Role of the Transport Layer

Before diving into TCP and UDP, it helps to understand what the transport layer is responsible for.

The transport layer sits between:

the application layer (web browsers, games, messaging apps)
the network layer (which moves packets across networks)

Its job is to make sure data moves between the correct applications on different computers.

This involves several responsibilities:

identifying applications using port numbers
managing data transmission
handling errors or lost packets
controlling communication speed

Different applications have different needs. Some require absolute reliability, while others care more about speed and low delay.

This is why two main transport protocols exist.

TCP: Reliable Communication

TCP (Transmission Control Protocol) is designed for reliable communication.

When an application uses TCP, the protocol works to ensure that:

all data arrives
packets arrive in the correct order
missing data is retransmitted

You can think of TCP like sending a registered package that requires confirmations along the way.

If something goes wrong, the system notices and corrects the problem.

Establishing a Connection

Before data is sent using TCP, the two computers first establish a connection.

This process ensures both sides are ready to communicate.

A simplified version of the process looks like this:

sequenceDiagram
  participant Client
  participant Server

  Client->>Server: SYN (Request connection)
  Server->>Client: SYN-ACK (Acknowledge)
  Client->>Server: ACK (Confirm)

This exchange is known as the three-way handshake.

Once the connection is established, data can begin flowing between the client and the server.

Ensuring Reliable Delivery

After a TCP connection is established, the protocol carefully manages how data moves across the network.

Packet Ordering

Each packet includes a sequence number.

This allows the receiving computer to:

detect missing packets
reorder packets that arrive out of sequence

Acknowledgements

After receiving packets, the receiver sends acknowledgement messages (ACKs).

If the sender does not receive an acknowledgement, it assumes the packet was lost and sends it again.

Flow Control

TCP also prevents the sender from overwhelming the receiver.

The receiving system tells the sender how much data it can handle at once.

This helps maintain stable communication between devices of different speeds.

Congestion Control

If the network becomes busy, TCP automatically slows down transmission.

This helps prevent network congestion from getting worse.

When TCP Is Used

Because TCP focuses on accuracy and reliability, it is used by many essential internet services.

Examples include:

loading websites (HTTP and HTTPS)
sending emails
downloading files
transferring data between servers

These activities require complete and correct data, even if it takes slightly longer to transmit.

UDP: Fast Communication

UDP (User Datagram Protocol) takes a very different approach.

UDP focuses on speed and simplicity rather than reliability.

When using UDP:

packets are sent without establishing a connection
packets are not acknowledged
lost packets are not automatically retransmitted

You can think of UDP like sending postcards through the mail.

You send them and assume they arrive, but you do not receive confirmation.

Connectionless Communication

Unlike TCP, UDP does not create a connection before sending data.

Packets are simply sent to the destination address.

A simplified interaction might look like this:

graph LR
  A[Application] --> B[UDP Packet]
  B --> C[Network]
  C --> D[Destination]

This makes UDP much lighter and faster, because there is less overhead involved in managing communication.

Why UDP Can Be Faster

UDP avoids many of the mechanisms used by TCP.

Specifically, UDP does not:

perform connection handshakes
track packet ordering
resend lost packets
manage congestion control

Because of this simplicity, UDP can deliver data with lower latency.

This makes it ideal for applications where speed is more important than perfect accuracy.

When UDP Is Used

UDP is commonly used for applications where small delays are worse than occasional data loss.

Examples include:

online gaming
live video streaming
voice calls over the internet
real-time broadcasting
DNS queries

In these situations, waiting for retransmissions would create noticeable delays.

For example, if a few packets are lost during a video call, it may cause a brief glitch — but the conversation continues smoothly.

Comparing TCP and UDP

Both protocols serve important roles on the internet.

The key difference is how they balance reliability and speed.

Feature	TCP	UDP
Connection required	Yes	No
Reliable delivery	Yes	No
Packet ordering	Guaranteed	Not guaranteed
Retransmission of lost packets	Yes	No
Speed	Slower due to overhead	Faster
Common uses	Web browsing, email, file transfers	Streaming, gaming, DNS

Neither protocol is “better” than the other.

Instead, each protocol is designed for different types of applications.

Key Ideas to Remember

The transport layer helps applications communicate across networks.

Two major protocols provide different communication styles:

TCP prioritizes reliability and ensures that all data arrives correctly.
UDP prioritizes speed and minimal delay.

TCP achieves reliability through:

connection setup
acknowledgements
retransmissions
flow and congestion control

UDP achieves speed by removing these mechanisms, allowing data to move more quickly through the network.

Understanding when each protocol is used helps explain how different internet services behave.

What Comes Next

Now that we understand how applications communicate using TCP and UDP, we can look more closely at how those applications are actually identified on a computer.

After all, a single device can run many networked programs at the same time — web browsers, messaging apps, game clients, and more. When packets arrive at a computer, the system needs a way to determine which application should receive them.

This is where ports and sockets come in.

Ports allow multiple applications to communicate over the network simultaneously, while sockets provide the interface programs use to send and receive data.

In the next chapter, we will explore how ports and sockets work together to connect network traffic to the correct application.