Design a highly available software-based load balancing topology

Load Balancer Requirements: • HTTP/HTTPS load balancer • Supports up to 100,000 HTTP requests per second • Supports up to 20,000 SSL RSA 2040 bits connection per second with SSL Offloading/Termination • SSL supports includes: SSL Offloading/Termination RSA 2048 bites or ECC 256bits certificates TLS 1.2 TLS cipher suites should support Perfect Forward Secrecy and be one of: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA the leaf server certificate hashing algorithm must be Secure Hash Algorithm 2 (SHA-2) with a digest length of at least 256 (that is, SHA-256 or greater). • High throughput and low latency load balancer. • Using commodity servers running Linux CentoOS • Horizontally scalable by adding new nodes • Highly available with no single point of failure solution. Active-Active setup is recommended. • Can run be deployed on any hosting provider where it does not requires any special networking configurations from the hosting/data center provider • Support Both IPv4 and IPv6 • Can use HAProxy, NGINX or any similar open source tools. Deliverables: 1) Solution topology and Design 2) Details Setup instruction for the different components of the proposed design