Bifalgorithm post

"Everyone knows what a load balance does, but very few know the algorithm that runs behind it. Let's break it down. First is Round Robin. So, in this request, we get one by one server. In this request, 1 is 1, 2 is 2, 3 is 3 is 3 and so on. And when all servers are used, the cycle starts again. Meaning, the fourth request will go again. Second, Least connection. This request counts not active connections. Meaning, when the most active users are the most active users, the next request is received. Perfect for web sockets, chat apps and live streaming. On third, we have waited round robin. Meaning, if a server is more powerful, it will automatically get more traffic. Meaning, 32 core servers and 8 core servers will never be equal to load distribution. On fourth, we have IP hash. In this, your IP address decides which request will go to the server. And in the next request, usually, same server you request this is login session and user state maintain this is the login session and user state maintain this is the login session and user state maintain this is the login session and user state maintain this is the login session and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state and user state"

"Everyone knows what a load balance does, but very few know the algorithm that runs behind it. Let's break it down. First is Round Robin. So, in this request,…