4 ms·

What sort of availability guarantees do you need? If you can tolerate a minute or two of less-than-full availability, Route53 DNS using geographical failover is

by mnutt 10y ago

What sort of availability guarantees do you need? If you can tolerate a minute or two of less-than-full availability, Route53 DNS using geographical failover is a decent solution.

sasas 10y ago
Looking at four 9s (4.38 min a month). Solution must be self hosted and not reliant on commercial cloud infrastructure.
- siculars 10y ago
  I'm at basho makers of Riak. If you're looking for ha at the db take a look.
  - sasas 10y ago
    Thanks. Not looking at HA with DB. I took a look at Riak briefly - looks interesting.
- wjossey 10y ago
  I haven't been in a situation where we had geographic redundancy and that small an SLA, and a commercial gear requirement. Ive got a couple of ideas, but most of them likely violate one of your requirements. The best advice I can give is to see if you can get someone from a large company that self hosts to chat with you. Not too many companies have the sort of requirements you're looking at, so it's going to be of the ilk of someone at Microsoft, Google, FB, Oracle, etc. Search your network, see if you've got a connection to someone on an SRE team there, and ask to buy them a coffee. :)
  - sasas 10y ago
    > Not too many companies have the sort of requirements you're looking at Telco is always the odd ball with redundancy. This requirement is somewhat relaxed. Generally mobile core networks are designed for 5 nines with geographical redundancy. This is all baked into the products and protocols (i.e SIGTRAN). In this instance i'm looking at traditional HTTP for an API that interfaces to location based services. One idea is to use DNS with the records dynamically modified based on availability monitoring and set the TTL very low. I see possible caveats with this solution though. Another idea could be to maintain sessions across sites and have an active/active setup with round robin. Traffic is then routed to the active site. The cost here is inter site bandwidth being wasted and additional complexity being introduced.
    - wjossey 10y ago
      Sasas I've got some thoughts that are probably easier done via a back and forth outside of HN. Hit me up on twitter if you use it: @dustywes
    - mnutt 10y ago
      Route53 is basically the solution you describe with DNS records, and you could build out anycast DNS servers yourself if you wanted. The main thing to be aware of is that not all clients respect TTLs. We set a 30s ttl and see a 99% switchover in about 60s but if you have some control over the clients you could probably go lower.

by mnutt 10y ago

What sort of availability guarantees do you need? If you can tolerate a minute or two of less-than-full availability, Route53 DNS using geographical failover is a decent solution.

sasas 10y ago

Looking at four 9s (4.38 min a month). Solution must be self hosted and not reliant on commercial cloud infrastructure.

siculars 10y ago
I'm at basho makers of Riak. If you're looking for ha at the db take a look.
- sasas 10y ago
  Thanks. Not looking at HA with DB. I took a look at Riak briefly - looks interesting.
wjossey 10y ago
I haven't been in a situation where we had geographic redundancy and that small an SLA, and a commercial gear requirement. Ive got a couple of ideas, but most of them likely violate one of your requirements. The best advice I can give is to see if you can get someone from a large company that self hosts to chat with you. Not too many companies have the sort of requirements you're looking at, so it's going to be of the ilk of someone at Microsoft, Google, FB, Oracle, etc. Search your network, see if you've got a connection to someone on an SRE team there, and ask to buy them a coffee. :)
- sasas 10y ago
  > Not too many companies have the sort of requirements you're looking at Telco is always the odd ball with redundancy. This requirement is somewhat relaxed. Generally mobile core networks are designed for 5 nines with geographical redundancy. This is all baked into the products and protocols (i.e SIGTRAN). In this instance i'm looking at traditional HTTP for an API that interfaces to location based services. One idea is to use DNS with the records dynamically modified based on availability monitoring and set the TTL very low. I see possible caveats with this solution though. Another idea could be to maintain sessions across sites and have an active/active setup with round robin. Traffic is then routed to the active site. The cost here is inter site bandwidth being wasted and additional complexity being introduced.
  - wjossey 10y ago
    Sasas I've got some thoughts that are probably easier done via a back and forth outside of HN. Hit me up on twitter if you use it: @dustywes
  - mnutt 10y ago
    Route53 is basically the solution you describe with DNS records, and you could build out anycast DNS servers yourself if you wanted. The main thing to be aware of is that not all clients respect TTLs. We set a 30s ttl and see a 99% switchover in about 60s but if you have some control over the clients you could probably go lower.