Can we use load balancer and reverse proxy together?
There is a discussion going on if it is possible to use one load balancer with reverse proxy?
This question is similar to this question, but my load balancer is different, and also I am not using Varnish. If it is possible, can I add the load balancer configuration in the config files of the reverse proxy? Or any other solution would be really helpful. It is possible to use a Load Balancer for routing (usually called a Proxy) and a reverse proxy (or more commonly a Server Load Balancer) for load balancing. This combination is very common in deployments with hundreds or thousands of servers.
There are a number of variations on this theme. The big difference is how the proxy and load balancer components handle server health. The most popular methods are:
Failover only the primary server in a cluster (LB and Proxies share health checks to the primary server). Failover the entire LB/proxy and allow only the primary server to respond to health checks (LB and Proxies share health checks to a single server). Only the LB/proxy handles health checks, and the LB uses some method to failover the primary server automatically (LB handles the failover and the primary server doesn't have to be restarted). For failover-only or failover-and-failover situations, you probably want to use LB and Proxies that can share health checks. Otherwise the load balancer will spend a lot of time trying to figure out if the LB should have been able to handle the health check request.
In your case you want to use failover-only, since you mention only having a few servers. In this case you'll want to use two load balancers: One for the LB and one for the proxy.
You may also want to consider a 3rd party solution like Citrix Netscaler instead of writing your own load balancer and proxy. It is generally considered to be easier to administer, and it will handle all of the complexities of LB and Proxy.
Is Nginx a load balancer or reverse proxy?
I have Nginx installed on my VPS as a reverse proxy, it is also a load balancer.
The simple answer is it's a load balancer. A reverse proxy will sit in front of an application and can provide several options: Access-Control-Allow-Headers: contains a list of headers that should be. Permitted to pass through. Auth-Methods: the authentication method, or set of methods, that the. Backend server(s) implements. Access-Control-Max-Age: the maximum time in seconds that the client can access a resource before being re-authenticated. Access-Control-Allow-Origin: when set, specifies a list of domains from which a request is allowed to make cross-origin requests. As it stands Nginx also has options for auth, but it falls short of having many options for the back end. You could setup some type of web server with authentication and a few plugins to handle the access controls.