Imagine you are sending an important message to a friend, but:

• messages may arrive late

• messages may arrive out of order

• some messages may never arrive

• you don’t know if the other person received them

That’s exactly what would happen on the internet without rules.

Computers need a proper way to:

• start a conversation

• send data safely

• know if data arrived correctly

• end the conversation cleanly

This is where TCP comes in.

What is TCP and why it is needed?

TCP stands for Transmission Control Protocol.

TCP is a set of rules that makes sure:

• data reaches the correct destination

• data arrives in the correct order

• missing data is resent

• both sides agree before talking and before stopping

In short:

TCP makes internet communication reliable.

Most important applications use TCP:

• websites (HTTP / HTTPS)

• emails

• file transfers

• APIs

Problems TCP is designed to solve

TCP exists because the internet itself is unreliable.

TCP solves problems like:

• data getting lost

• data arriving out of order

• duplicate data

• sending data too fast for the receiver

Instead of assuming everything works, TCP checks and confirms at every step.

What is the TCP 3-Way Handshake?

Before any data is sent, TCP first establishes a connection.

This process is called the 3-Way Handshake.

Think of it like starting a phone call:

1. “Can I talk to you?”

2. “Yes, I’m ready.”

3. “Great, let’s start.”

Only after this do both sides start sending data.

Step-by-step: SYN, SYN-ACK, ACK

Step 1: SYN (Client → Server)

The client sends a SYN message.

Meaning:

“I want to start a connection.”

It also sends a sequence number, which is like:

“This is my starting point.”

Step 2: SYN-ACK (Server → Client)

The server replies with SYN-ACK.

Meaning:

“I got your request, and I’m ready too.”

Here the server:

• acknowledges the client’s sequence number

• sends its own sequence number

Step 3: ACK (Client → Server)

The client sends ACK.

Meaning:

“I received your response. Let’s start talking.”

Now the connection is established.

Both sides are synchronized and ready to send data.

How data transfer works in TCP

Once the connection is open, data flows both ways.

But TCP doesn’t send data blindly.

It:

• breaks data into smaller chunks

• numbers each chunk

• waits for confirmation

Each chunk has:

• a sequence number

• an ACK number from the receiver

This helps TCP track everything accurately.

How TCP ensures reliability, order, and correctness

1. Sequence Numbers

Every piece of data is numbered.
This ensures:

• correct order

• no missing pieces

2. Acknowledgements (ACK)

The receiver confirms:

“I got data up to this point.”

If the sender doesn’t get an ACK, it assumes something went wrong.

3. Retransmission

If data is lost:

• sender resends only the missing part

• not the whole data again

4. Flow Control

TCP avoids overwhelming the receiver by:

• sending data at a safe speed

• adjusting based on receiver’s capacity

This keeps communication smooth.

How a TCP connection is closed

Just like starting a connection, closing it also follows rules.

TCP uses FIN and ACK.

Step 1: FIN

One side says:

“I’m done sending data.”

Step 2: ACK

The other side replies:

“I received your finish request.”

Step 3 & 4: Repeat from other side

The second side also sends FIN, and the first side replies with ACK.

Now the connection is fully closed.

TCP connection lifecycle

1. Connection established (3-way handshake)

2. Data transferred reliably

3. Connection closed cleanly