How is load balancing organized?

Question

Nginx

Hello everyone.
I will say right away that I am studying the issue, and it is a little difficult to figure it all out.
I need to organize a large load balancing over https.
I was offered NGINX, a good choice. It acts as a proxy server. But how to scale it? and how to achieve stability failure? Will he, in fact, eventually act as a bottleneck?
I can not find information on this issue normally, especially about scaling.
Are there any other options for load balancing?
And in NGINX it is fashionable when it works without restarting it to add or change to whom it redirects.
And will WSS work through it?

Answer 1

real balancing is much more difficult. NGINX is simply a tool for distributing traffic across multiple servers. In fact, the system should (ideally) consist of a DNS server that communicates with Service Discovery (for example, Consul), in which both the application server and the balancer server A are registered. Attention - there should be several balancers and all this should be tied to DNS so as not to get stuck due to fixed IPs. The same application server must have traffic from at least two load balancers

Answer 2

Here are the methods of balancing through nginx. Only the version built with the sticky module may be required

Answer 3

You can also google about Traefik, Caddy, HAProxy