I know how to setup these solutions:
Let's say the website
www.example.com
has a single machine for it (IP 203.0.113.123), using a Linux + Apache server. It works if the bandwidth is not too high.Let's say we now have more and more requests for this website, thus the computer with IP 203.0.113.123 will now only be a load-balancing server, dispatching the requests to many workers (other computers), which serve the actual webpages.
but I have a question about this case:
- Let's say now there are sometimes peaks of tens or hundreds of thousands of requests per second for this website. Having a single load-balancing machine 203.0.113.123 is not possible anymore.
If we have 10 load-balancing machines: 203.0.113.123, 203.0.113.124, 203.0.113.125, 203.0.113.126, 203.0.113.127, ..., 203.0.113.132 (that dispatch the requests to tens of other workers), how to have the clients arrive to all of them, randomly / Round-robin-style?
The DNS records usually display only one A record, even for big well-known websites (see here the DNS records for Google, there is only one A record), such as:
www.example.com 3600 A 0 203.0.113.123
How to make that clients' requests arrive to the ten machines randomly and not only 203.0.113.123?
(Obviously, we don't want a single machine to dispatch the requests to the ten load-balancing machines, because then we would be back to case 2.)
0 Answers