출처:
https://hoing.io/archives/8607
https://d2.naver.com/helloworld/605418
https://velog.io/@i01029407043/%ED%94%84%EB%A1%A0%ED%8A%B8%EC%97%94%EB%93%9C-HTTPS-%EC%82%AC%EC%9A%A9%ED%95%98%EA%B8%B0-AWS-EC2-Route53-Load-Balancer
https://blog.naver.com/ehroh12/222845547842
https://duckracoon.tistory.com/entry/DNS%EC%9D%98-%EA%B0%9C%EB%85%90-feat-Route53-%EC%99%9C-%EC%93%B0%EB%8A%94%EA%B0%80
(영문 해석)
Each device connected to the Internet has a unique IP address which other machines use to find the device. DNS servers eliminate the need for humans to memorize IP addresses such as 192.168.1.1 (in IPv4), or more complex newer alphanumeric IP addresses such as 2400:cb00:2048:1::c629:d7a2 (in IPv6).
Load balancing refers to efficiently distributing incoming network traffic across a group of backend servers, also known as a server farm or server pool.
Modern high‑traffic websites must serve hundreds of thousands, if not millions, of concurrent requests from users or clients and return the correct text, images, video, or application data, all in a fast and reliable manner. To cost‑effectively scale to meet these high volumes, modern computing best practice generally requires adding more servers.
A load balancer acts as the “traffic cop” sitting in front of your servers and routing client requests across all servers capable of fulfilling those requests in a manner that maximizes speed and capacity utilization and ensures that no one server is overworked, which could degrade performance. If a single server goes down, the load balancer redirects traffic to the remaining online servers. When a new server is added to the server group, the load balancer automatically starts to send requests to it.
Source:
https://www.f5.com/services/resources/glossary/load-balancer
https://www.nginx.com/resources/glossary/load-balancing/
https://www.cloudflare.com/learning/dns/what-is-dns/