We're currently using OVH Load Balancers to serve our LAMP stack webapplication.
The problem is, that OVH LB services are really not that great and is down too much. The servers are also located with OVH, but they got a great uptime percentage, and we're therefore happy about those services.
So at the moment I'm trying to find a better solution to load balance our LAMP stack and also having the new load balancing handle fail-over if one of the servers are down.
I'm thinking about setting up
nginx on a single server to act as a software load balancer, but need to know if I can manage cookies which that setup or if there is a more suitable setup.
Ours clients got their own subdomain as an entrance to their portal, and we can setup a domain per server if needed, so the setup would be something like:
Entry-point: https://client.brandname.com Application server 1: https://client.brandname1.com Application server 1: https://client.brandname2.com Application server 1: https://client.brandname3.com
But we hold a sesson-key and a token within 2 sets up cookies named
We need those cookies to be created, read, modified and deleted by the application servers, so they need to be passed through the Load Balancer proxy, is this a possibility with the nginx load balancer setup?
So basically, can this be done via the nginx load balancer or is there a more suitable approach?