1 IntroductionIn this project, we would implement a simple TCP layer load balancer (in essence similar to HAProxy (haproxy.org). The main objectives of this assignment can be summarized as follows:...

1 IntroductionIn this project, we would implement a simple TCP layer load balancer (in essence similar to HAProxy (haproxy.org). The main objectives of this assignment can be summarized as follows: (1) hands-on experience with“UNIX” sockets, (2) deep understanding of HTTP protocols, and (3) an introduction to system design, andperformance monitoring.2 Multi-threaded Load Balancer2.1 SpecificationsYour balancer server should accept incoming connection requests, and select one of the backend servers (according to a policy) to forward the request to. The response is forwarded back to the client. A log entry wouldbe added including the following information: (a) client ip, (b) client port (c) Request Type (i.e., GET, Post,..), (d) the chosen server ip, (e) the size of the request, (f) the size of the response, (g) the status code of theresponse, (h) time of the request and the time of the response.The load balancer should implement two policies. Policy I is a simple round robin , where servers are chosenin order. Students should propose another policy. You can use the log entries, or propose new metrics to thelog.The solution should be working and running, you an use any backend http webserver (including Apachehttpd).
3 Bonus3.1 HTTP 1.1Using persistent connections to the backend servers, can significantly improve the performance. This can bedone by using HTTP 1.1 and reuse the connections.3.2 X-Forwarded-ForAdd X-Forwarded-For to the request to the back end server. For more information, please check this https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For.