[154379] in North American Network Operators' Group
Re: FYI Netflix is down
daemon@ATHENA.MIT.EDU (Rodrick Brown)
Tue Jul 3 11:36:51 2012
In-Reply-To: <1C7B96053DD7814496A0D1E71661B68302CF5CEA@SMF-ENTXM-001.sac.ragingwire.net>
From: Rodrick Brown <rodrick.brown@gmail.com>
Date: Tue, 3 Jul 2012 11:35:06 -0400
To: Dan Golding <dgolding@ragingwire.com>
Cc: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jul 3, 2012, at 9:11 AM, "Dan Golding" <dgolding@ragingwire.com> wrote:
>> -----Original Message-----
>> From: James Downs [mailto:egon@egon.cc]
>>=20
>>=20
>> On Jul 2, 2012, at 7:19 PM, Rodrick Brown wrote:
>>=20
>>> People are acting as if Netflix is part of some critical service
> they
>> stream movies for Christ sake. Some acceptable level of loss is fine
>> for 99.99% of Netflix's user base just like cable, electricity and
>> running water I suffer a few hours of losses each year from those
>> services it suck yes, is it the end of the world no..
>>=20
>> You missed the point.
>=20
> And very publically missed the point, too. The Netflix issues led to a
> large discussion of downtime, testing, and fault tolerance that has been
> very useful for the community and could lead to some good content for
> NANOG conferences (/pokes PC). For Netflix (and all other similar
> services) downtime is money and money is downtime. There is a
> quantifiable cost for customer acquisition and a quantifiable churn
> during each minute of downtime. Mature organizations actually calculate
> and track this. The trick is to ensure that you have balanced the cost
> of greater redundancy vs the cost of churn/customer acquisition. If you
> are spending too much on redundancy, it's as big of mistake as spending
> too little.=20
I totally got the point and the last bit of my post was just tongue in cheek=
.=20
As I stated in my original response it's very unrealistic to plan for every p=
ossible failure scenario given the constraints most businesses face when imp=
lementing BCP today. I doubt Amazon gave much thought to multiple site outag=
es and clients not being able to dynamically redeploy their engines because o=
f inaccessibility from ELB.
>=20
> Also, I don't think there is an acceptable level of downtime for water.
> Neither do water utilities.=20
>=20
> - Dan
>=20
