What Is The Difference Between TCP And UDP Explain?

TCP is a reliable protocol. There is an acknowledgement for each TCP packet.
In UDP there are no acknowledgements. That means the sender does not know if a packet is received by the receiver.

In TCP if an ack (acknowledgement) is not received for a long time, the sender sends the same packet again to ensure that each packet is properly received in the other end.

In TCP protocol it is handled in such a way as to not to repeat the same packet if received twice and not to lose any packet. There are sequence numbers and acknowledgement numbers to each TCP packet.

IP is in a lower level than TCP or UDP. There can be TCP/IP or UDP/IP. IP means Internet protocol. TCP means Transport Control Protocol.

The main difference between the UDP and TCP protocol is that the UDP is connectionless protocol while the TCP is a connection oriented protocol.let me explore both of these protocols a bit more.

The simple unreliable transport layer protocol in internet is known as User Datagram Protocol (UDP). It is a connectionless and unreliable transport protocol. It does not add any thing to services or IP except for providing process to process communication instead of host to host communication. It also provides some very limited error checking. UDP is a simple protocol Sand have minimum overhead. If a process wants to send very small message and does not care about reliability, UDP can be used there. It is very convenient protocol for applications of multimedia and multicasting. UDP packets are known as user datagram. The header of these packets has fixed size that is 8 bytes. TCP is a reliable but a bit complex protocol. This protocol is a transport layer protocol. TCP is an abbreviation of Transmission Control Protocol. Unlike UDP protocol, this protocol is connection oriented protocol. AS the UDP does, TCP also uses port numbers as the transport layer addresses. TCP keeps all the bytes in a buffer until it receives an acknowledgment.

TCP has to create a "handshake" between two nodes prior to sending a data and negotiate the session in sync like: Are you ready? Yes, Acknowledged. OK. I'm going to send a block... Received. .. Also, TCP/IP has built in data recovery, re-transmit, correction etc.

UDP - is a "wild" TCP/IP. Meaning, hey I'm going to transmit at... Anybody can tune-in. What? You didn't get some frames? Sorry there are no checks, corrections and validations since I'm very fast and do not want being bothered by some individual negotiations. Anybody just tune-in and catch what you can...