Hi Mohammed.
Yes HAProxy supports all of the requested capacity and features from
below. For a nice example what HAProxy is able to handle can you read
this Blog post.
https://www.haproxy.com/blog/haproxy-forwards-over-2-million-http-requests-per-second-on-a-single-aws-arm-instance
The very detailed Documentation can be found in the Web
https://docs.haproxy.org/ or in the source repository under the doc
directory
https://git.haproxy.org/?p=haproxy.git;a=tree;f=doc;h=9a53977a683fd7e80f23fff2a18ef192ca908636;hb=HEAD
There are very good examples and explanations for HAProxy features on
the HAProxy com Blog page https://www.haproxy.com/blog and you can also
find some examples with your favorite Search engine. Please take care
that some search results refer to some previous HAPRoxy Versions which
are not maintained anymore, this means that the founded solution could
work or need some rework for the current versions.
HAProxy have two versions the Opensource one and the Enterprise one.
If your company want support and is willing to pay for that can you get
in touch with HAProxy Sales via the contact from
https://www.haproxy.com/contact-us for the HAProxy Enterprise version
https://www.haproxy.com/products/haproxy-enterprise.
Hth with best regards
Alex
On 2023-10-13 (Fr.) 09:41, Mohammed Anees A wrote:
Hi Team
We have a requirement to for a Software based NLB to Load Balance an
enterprise application.
Following are the Capacity and Features of NLB required. Please
confirm, does HA Proxy supports the below capacity and features ?. let
us know the licensing model and Support structure.
Capacity :
* Requests per Second = 5000 RPS
* Concurrent Connections = 5000 Concurrent Sessions.
* Throughput = 40 Mbps
Features :
1. *Routing Profile *
Routing profile can be TCP based (layer 4) or HTTP based (layer 7).
**
2. *Load Balancing Method*
All load balancing methods are supported. It is recommended to use
Least Connections or Round Robin load balancing methods, for better
distribution between Application servers.
3. *Session persistence (stickiness)*
The LB must be configured with session persistence to enable a session
connection with the same application server instance. Configure
session persistence in all levels of load balancing (for example, if
there is a global load balancer in front of a few local load balancers).
To achieve session persistence, configure the LB with one of the
following persistence profiles:
* HTTP Cookie
* Client IP (Source address)
4. *Health monitoring*
**
An important property of an LB is the ability to perform health
monitoring checks (heartbeats) on each Application server. By using
health monitors, the LB verifies the server response or checks for any
network problems that can prevent a client from reaching a server. By
doing so, the LB can place the server in or out of service and can
make reliable load-balancing and high availability decisions.**
A common and recommended health monitor is *HTTP GET Request.***
5. *Idle (execution) timeout*
Setting the execution timeout controls termination of idle
connections. Configure an execution timeout of at least 4 hours.
6. *HTTPS Configuration*
The load balancer supports several HTTPS configuration methods.
These include:
* SSL bridging
* SSL offload
* SSL pass-through
SSL bridging and SSL offload are supported in HTTP based routing
(layer 7), and require deploying TLS certificate on the LB. SSL
pass-through is supported in TCP based routing (layer 4), and does not
require deploying a certificate on the LB.
Regards
Mohammed Anees
+91 9944170656
