Stateful and stateless in Protocol

1. Overview

Network Protocols for web browser and servers are categorized into two types: stateless Protocol, and Stateful protocol. Both protocols are differentiated on the basis of the requirement of server or server-side software to save status or session information.

 

2. Comparisons

STATELESS PROTOCOL	STATEFUL PROTOCOL
Does not require the server to retain the server information or session details	Require server to save the status and session information
No tight dependency between server and client	Tight dependency between server and client
Simplify the server design	Makes the design of server very complex and heavy
Works better at the time of the crash because no state that must be restored, a failed server can simply restart after a crash	Does not work better at the time of crash because the stateful server has to keep the information about the status and session details of the internal states.
Handle the transaction very fastly	Handle the transaction very slowly
Easy to implement in internet	Logically heavy to implement in internet
Require fewer resources because the system does not need to keep track of the multiple link communications and the session details	Require more resources to keep track of the multiple link communications and the session details
IP, HTTP, UDP, DNS	TCP, FTP, Telnet

 

3. References

https://en.wikipedia.org/wiki/Stateless_protocol

https://en.wikipedia.org/wiki/State_(computer_science)

https://en.wikipedia.org/wiki/Internet_Protocol

https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol

https://www.geeksforgeeks.org/difference-between-stateless-and-stateful-protocol/