TCP
The Transmission Control Protocol (TCP) is a connection-oriented service where the data transmission is on both sides after the connection is established. It has an in-built system to check on the errors as well. In addition, the system also guarantees that the data get delivered in the order it was sent.
This is the better option for transferring information such as data files, web pages, images, etc. However, the feedback mechanisms result in a larger overhead that helps for the good use of available bandwidth on the network.
UDP
Further, the User Datagram Protocol (UDP) is a connectionless internet protocol. In the UDP, neither recovery nor error-checking checking services are needed. The data is repeatedly sent to the receiver whether the receiver is ready or not and is not responsible for end-to-end communication.
There is no overhead to open, maintain, or terminate a connection. We can see the protocol in real-time communications like broadcast transmissions or multicast network ones. Comparatively, UDP is faster than TCP and is much more efficient.
TCP Vs. UDP
| S.N. | TCP | UDP |
|---|---|---|
| 1. | This is connection-oriented. | This is connectionless. |
| 2. | This is reliable. | This is unreliable. |
| 3. | The data delivery is guaranteed. | The data delivery is not guaranteed. |
| 4. | TCP is comparatively slower than UDP. | UDP is comparatively faster than TCP. |
| 5. | Broadcasting is not supported. | There is broadcasting support. |
| 6. | Lost packets can be retransmitted. | Lost packets cannot be retransmitted. |
| 7. | It has sequence delivery. | It has no sequence delivery. |
| 8. | It has acknowledgment. | It has no acknowledgment. |
| 9. | It has handshaking. | There is no handshaking signal. |
| 10. | Use cases: - (HTTP & HTTPS & SMTP & POP & FTP) | Use cases: - (Video Streaming & DNS & VoIP) |
pragyaasapkota
/
System-Design-Concepts
Though the concepts of system design might be tricky, let's see them individually to their core concepts and have a better understanding.
System Design
Systems design is the process of defining elements of a system like modules, architecture, components and their interfaces and data for a system based on the specified requirements.
This is a index for the concepts of system.
If you wish to open these in a new tab, Press CTRL+click
| S.N. | Table of Content |
|---|---|
| 1. | Caching |
| 2. | Network Protocols |
| 3. | Storage: The Underrated Topic |
| 4. | Latency and Throughput |
| 5. | System Availability |
| 6. | Leader Election |
| 7. | Proxies |
| 8. | Load Balancing |
| 9. | Endpoint Protection |
| 10. | HTTPS: Is it better than HTTP? |
| 11. | Polling and Streaming |
| 12. | Long Polling |
| 13. | Hashing |
| 14. | CAP Theorem |
| 15. | PACELC Theorem |
| 16. | Messaging and Pub-Sub |
| 17. | Database |
| 18. | Logging, Monitoring, and Alerting |
| 19. | Distributed System |
| 20. | Scaling |
| 21. | Event Driven Architecture (EDA) |
| 22. | CQRS |
| 23. | Message Queue |
| 24. | Architectural Patterns |
| 25. | Enterprise Service Bus (ESB) |
I hope this article was helpful to you.
Please don’t forget to follow me!!!
Any kind of feedback or comment is welcome!!!
Thank you for your time and support!!!!
Keep Reading!! Keep Learning!!!
Top comments (0)