The SO_REUSEPORT socket option
The SO_REUSEPORT socket option
Posted Feb 8, 2014 18:19 UTC (Sat) by batth.maninder@gmail.com (guest, #81449)In reply to: The SO_REUSEPORT socket option by giraffedata
Parent article: The SO_REUSEPORT socket option
The ability to route to same tuple sounds like premature optimization. For example, if i have spawned few stateless servers, and if a connection request arrives, it would simply sit in queue till the original server is ready? Most typical architecture for stateful servers is to spawn 3 of them on different physical machines for reliability purposes and have load balancer perform sticky sessions. Another option is to spawn stateless servers with distributed cache to maintain cache. The ability to route connections and even datagrams to the same tuple is really an "application" level concern. What is the original server tuple is not running any more? Do i need to plug in policies for SO_REUSEPORT to determine how to handle failure conditions?
Posted Jun 2, 2020 21:14 UTC (Tue)
by nilsocket (guest, #135507)
[Link]
It isn't meant to replace load balancers or something similar.
Maybe within a single application, with multiple threads to handle the load, seems like a good option to have.
The SO_REUSEPORT socket option
I think, one should remember that, this is done for the sake of performance, for those who need it.