Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Keep a static "emergency mode" site on S3

coderwall.com

Post reply on HN
Print view View original

81–85 of 85 posts

Re: Keep a static "emergency mode" site on S3

#81

Post by EGreg »

Retric wrote: post #73
EGreg wrote: post #62

Earlier quoted context omitted.

Actually it's a great way to simultaneously design a website AND an api for others to use. It's also a great way to separate concerns. It's also a great way to reduce load on your server. In fact, it's an easy way to have some people code a standard back end with a standard authentication so that some other people can make front ends for the web, iphone, and more. You can use, for example, oauth to authenticate with…

I dont't think we are quite on the same page, having an public API etc is wonderful but let's use a slightly different topic. Using some 3rd party ORM to talk to your database is generally a no brainer, but v0.1 might not even have a database yet because persistence is not generally needed for a demo. Why put off such a core feature, because just changing your objects is less friction so and the goal is to see if any…

Because it's just as easy to code your front end independently and then hook up your back end to it. If the front end is static, it can be completely hosted on a CDN. If your back end is unreachable the front end can just take another code path. There's your 0.1

Re: Keep a static "emergency mode" site on S3

#82

Post by revertts »

tszming wrote: post #78
colmmacc wrote: post #29

(I work on Route 53). As __lucas has mentioned, this can be achieved with Route 53 Failover, which we'd recommend. Route 53 Failover is (hopefully) pretty easy to configure. Just mark your ELB as the primary and enable target healthchecks, and add the S3 website bucket as the secondary. We'd also suggest that you use an S3 website bucket hosted in a different region than your ELB. This should take no more than a minu…

The current R53 health check does not support SSL endpoints, which is rather critical for our use-cases. Please make it happen, thanks.

Depending on your use case, you might be able to get away with a TCP check on 443 or a separate, HTTP accessible deep healthcheck.

Re: Keep a static "emergency mode" site on S3

#83

Post by jedberg »

hboon wrote: post #76
jedberg wrote: post #59

Earlier quoted context omitted.

Except that his way all the traffic instantly switches, and your way you have to wait for DNS propagation, which about 15% of the users on the internet will not pick up for over a week. DNS is an awful way to do failover.

In your experience, are there still major ISPs that don't respect DNS TTL?

Yes, about 15%. :) To be fair most flip within 24 hours, but about 3% or so take longer than a week.

Typically rural ISPs or Alaskan ISPs (they don't want to pay to forward all the requests so they override the TTLs).

This is when we flip Netflix IPs.

Re: Keep a static "emergency mode" site on S3

#84

Post by jedberg »

colmmacc wrote: post #61
jedberg wrote: post #59

Earlier quoted context omitted.

Except that his way all the traffic instantly switches, and your way you have to wait for DNS propagation, which about 15% of the users on the internet will not pick up for over a week. DNS is an awful way to do failover.

To your point ; it's ok to do both. Route 53 supports DNS TTLs as low as 0 seconds. ELB and S3 endpoints both have 60 second TTLs. My experience with flipping names like www.amazon.com doesn't reflect the 15% figure. I've seen about 97% of web traffic honouring the TTL and flipping quickly. Within 5 minutes almost all of the rest too. We also take CloudFront sites in and out of service for maintenance, and in 5 years…

When we flip Netflix domains we see about a 15% straggler effect (although to be fair only about 3% take a week, but many take around 24 hours).

Re: Keep a static "emergency mode" site on S3

#85

Post by revertts »

jedberg wrote: post #84
colmmacc wrote: post #61

Earlier quoted context omitted.

To your point ; it's ok to do both. Route 53 supports DNS TTLs as low as 0 seconds. ELB and S3 endpoints both have 60 second TTLs. My experience with flipping names like www.amazon.com doesn't reflect the 15% figure. I've seen about 97% of web traffic honouring the TTL and flipping quickly. Within 5 minutes almost all of the rest too. We also take CloudFront sites in and out of service for maintenance, and in 5 years…

When we flip Netflix domains we see about a 15% straggler effect (although to be fair only about 3% take a week, but many take around 24 hours).

How much of that 15% is driven by ISPs versus misbehaving clients? (eg. set to boxes)
Post reply on HN