All language subtitles for 8. UDP vs TCP

Well, hi, guys.

Hey.

So in this lesson, guess what, we're going to learn some differences between UDP and TCP because I

know you had those questions bubbling around in your head.

So let's get started right away.

So remember when I said way back in the beginning, the IP cannot distinguish between communication

programs running on the same computer because when you look at the package structure, I'll tell you

why, by the way.

And so when you look at the package structure, you will see that only source and destination addresses

are used.

Right?

But in reality, many programs can run on two different computers let's say computer a computer b,

and they communicate with each other.

So these programs are separated from each other by the protocols used in the transport layer.

IP uses two protocols and the transport layer, and these protocols are the UDP or user data, grim

protocol and TCP or transmission control protocol.

So UDP is a connection less protocol, and TCP is a connection based protocol.

All right.

So we've got UDP.

This is one of the protocols that applications used to transfer data.

OK.

Now, the created UDP packets are encapsulated by IP and transported in the IP environment.

So no prior connection is required to carry UDP packets.

UDP packet structure is as simple as shown in the figure here.

The header consists of eight bytes, followed by the data field.

The UDP packets are also called segments.

And the source and the destination ports indicate through which ports, the nodes, whose addresses

are given in the IP data, grams will carry out this communication.

Excellent.

So UDP length reports the length of the hadarin data field.

Air testing may not be used in UDP.

UDP is a pretty simple protocol, so it doesn't deal with issues like resending loss data or flow control.

It creates an interface for the use of IP.

So it's preferred in real time applications because of its simplicity.

Now, UDP can also be used in applications where short request and responses are migrated.

UDP connections do not need to be set up or released.

So actually, nothing is done for lost UDP segments.

Now, an advanced computer networks, the UDP protocol has been developed in order to create a data

graham mode and packet switched computer communication.

That said, protocol includes a procedure for sending a message from one application program to another

with minimal protocol mechanisms.

Applications that want the package guarantee.

We'll also use the TCP protocol.

So UDP, which is used in real time data transfers, such as image and audio transmission in wide area

networks called when also minimizes data transmission time since it does not perform flow control and

connection establishment processes.

Now, if TCP and UDP use the same communication path, the service quality of that real time data transfer

with UDP will decrease due to the high data traffic created by TCP.

So protocols that use the UDP.

Well, they include TFTP, DNS and as MP.

Application programmers often prefer UDP over TCP, and that's because UDP does not take up much bandwidth

on the network.

Now, you could probably characterize UDP as an unreliable transport protocol because after sending

the packet over to the network, it doesn't care whether it's sent or not.

It doesn't even keep track and therefore it doesn't have the authority to confirm whether the packet

has reached its destination or not, or even can.

So applications that want to send data securely over UDP.

Well, they've got to do so on their own methods.

So UDP is a protocol that focuses on exchanging a few messages as possible and operates at the transport

layer.

And it really does not guarantee whether the data is transmitted correctly or incorrectly.

It just doesn't care.

So now some more these differences between UDP and TCP.

The TCP protocol guarantees sequential sending a packet, while of course UDP does not.

TCP packets contain a sequence number in the header information.

UDP does not.

That's why TCP always requests the next packet.

So in other words, if a different package is received, it notifies the other party and changes the

package that should arrive first and puts that forward.

So UDP could not come anywhere close to doing any of that.

Right.

Now, unlike the UDP protocol, TCP IP guarantees security because TCP IP checks with acknowledgement.

So in other words, when the package sent, the other party considers that packet as unsent sends it

again without informing that it has received the packet.

And then in addition to that, it keeps control information in the header information in order to understand

whether the packet is going correctly.

So UDP also keeps control information, but if this control is wrong, it's not going to request the

same packet again.

So TCP establishes an uninterrupted connection until the process terminates, while UDP cannot.

UDP only connects when data is to be sent and then disconnects when the process is finished.

All right, so that's enough of this UDP and TCP stuff, but now you know the differences in why one

is used over the other.

We've got great stuff coming up for you now that, you know, all that.

So I'll see you on the other side.