Hacker News new | past | comments | ask | show | jobs | submit login

I think you have a misconception on what actual reliability is for more products and services. 99.999% is a solid service, 99.99999% is a hard to achieve target for enterprise software.

To say Google is not the place to look for reliability is a pretty comical statement.

For reference, 99.999 is 5 mins of downtime/year.

99.99999 is 3 seconds of downtime/year.

As you get beyond 5 nines, environmental factors begin to dominate (if the service is networked: network unavailability, if the service is onsite, power outages and weather) any reliability inherent in the service.

I don't have a misconception. Can you name a single internet service that has an actual five nines availability? That's definitely not google search nor gmail.

I never claimed Google has 5 9s. Your claim that 99.999% for Gmail means Google isn't a place we should go to for reliability advice is comical at best, ignorant at worst.

I couldn't make that claim, because Gmail is very far from 99.999%. I merely pointed out that SRE quote is wrong, that's the quality of reliability advice they give. I generalized it, because I've seen plenty of bad reliability advices coming from Google, even burned by some of them in the past.

If you are into reliability you really shouldn't take Google seriously.

What specifically are you disagreeing with in the quote? It does not say that Google is five nines, nor does it say whether or not five nines is desirable.

The argument is basically the following:

(1) Consider the claim that getting to 100% reliability is important.

(2) If the claim were true, then it would be important to go from 99.999999999999999% availability to 100%.

(3) That is obviously not important, so the claim must be false.

(4) Since we have shown that the best target value is not 100%, it must be some number x, with x < 100%.

Google cloud spanner has an availability SLA of 5 9s if you use multiple regions [0]. Not cheap though.

[0]: https://cloud.google.com/spanner/sla

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact