News for hackers. Stuff that matters.

A comment on Moving from AWS to Bare-Metal saved us 230k$ /yr. Parent comment

Re:Moving from AWS to Bare-Metal saved us 230k$ /yr by threeseed on Thursday November 16, 2023 @05:12PM (#38296327)
Still need to synchronise data, update DNS records, wait for TTLs to expire.

HA architectures exist for a reason because that last step is a massive headache.

[ Parent | on HN ]
Re:Moving from AWS to Bare-Metal saved us 230k$ /yr by quickthrower2 on Thursday November 16, 2023 @05:52PM (#38296791)
They need to do fire drills and practice this maybe daily or at least weekly? Failover being a normal case. Can’t you do failovers in DNS?
[ Parent | on HN ]
Re:Moving from AWS to Bare-Metal saved us 230k$ /yr by threeseed on Thursday November 16, 2023 @06:11PM (#38296993)
A significant percentage of users will still have their DNS resolver chain caching the old host.

Because TTLs are a guide not mandatory. And many companies/ISPs ignore it for cost reasons.

[ Parent | on HN ]
Re:Moving from AWS to Bare-Metal saved us 230k$ /yr by BackBlast on Thursday November 16, 2023 @07:03PM (#38297435)
Yes, you can do it in DNS. Update the record with your new ingress, then wait for the timeout on the old record to assert itself and the new connections move over.

Not all DNS servers properly observe caching timeouts, so some customers may experience longer delays before they see it working again.

[ Parent | on HN ]