All geek questions in one place

AWS DNS Failover Alternative?

I recently started reading and playing with AWS. I am particularly interested in the various high-availability architectures that can be implemented using the platform. In particular, I am looking for a reliable solution for poor people, which can be implemented using the least number of servers .

So far, I am satisfied with the solutions for the main HA tasks: load balancing, redundancy, automatic recovery, scalability ...

The only thing I have is fault tolerance solutions .

Using the ELB may seem like great, but the ELB actually uses DNS balancing under the hood. See Is AWAS Elastic Load Balancer the Only Failure Point? . Also from a Netflix Blog Post: Netflix Lessons Learned from AWS Outage

This is due to the fact that ELB is a load balancing scheme between two levels. The first tier consists of basic DNS-based load balancing. This gives the customer an ELB endpoint in the cloud that is located in one of the zones that your ELB is configured to use.

Now I learned that switching DNS is not an ideal solution, as others have pointed out, mainly because of the unpredictable DNS caching. See For example: Why DNS failover is not recommended? .

ELB, , AWS HA DNS 53.

, IP/Elastic IP (EIP) , IP- IP- Fail-over, , . , , , . , , .

, ?

, , , DNS 2 :

  • 2 EC2 AZ. -, , , .

  • 1 ELB 2 EC2 A, 1 ELB 2 EC2 B. , . 1 ELB ?

+4
1

ELB, , , .

"1" ELB, 2 , 1, 2. 2 IP-, 2 A , , TTL.

AZ, AZ ( , 1 AZ).

IP- , , , ELB , , 30 , , -, , ELB DNS .

, DNS . 53 ( 53), , DNS, .

, / Elastic IP HAProxy . HTTP , ELB, . , . EIP . HAProxy ELB , , - . ( ​​ , AWS, - .)

+2

Source: https://habr.com/ru/post/1610522/

More articles:


All Articles