3 ms·
DNS round-robin with mirror servers that run 24/7.
by ck2 15y ago
DNS round-robin with mirror servers that run 24/7.
- brador 15y agoYup, this is what I'd do. Mirroring would be the big issue, but not that big a deal unless data was time critical.
- ck2 15y agoSites with large amounts of data do this in realtime all the time. WordPress.com for example has five mirrors (maybe more by now).
- viraptor 15y agoVarious DNS caching architectures deployed by ISPs will sometimes strip additional addresses, or choose one for you themselves. That means if you're unlucky, that selected address will be down. Even if they do handle DNS correctly, hitting a dead server and failing over to the next one (possibly also dead) can take some time and may be interpreted as service not working. Unless you control the whole path to the customer and his client application, DNS is not a solution for either HA or LB. (found out after trying to come up with something close to 100% for voip network - LB with 2 DNS entries on public internet will give you split close to 70-30) Another question is how is the downtime interpreted? If you're halfway through some transaction / flow and the site you're talking to goes down, should your flow (shopping basket for example) be available on the failover site?