Merry Christmas to you, love throwing those cords on the fire!
HA HA HA. Thought about doing a post on the big Netflix AWS debacle but hey, it’s Christmas…
Well, Greg, my OTA was unaffected. My Plex server was unaffected. I actually did not know there was an outage until I looked at Drudge.
Here in San Diego Netflix was a no go. merry Christmas Len!
Merry Christmas, Greg. Been reading the postmortems on the Netflix outage. There was a lot of finger pointing, but no real data on the failure or likelihood that it will happen again or become common.
Personally, I have always been skeptical about streaming HD content over the internet. If we have reached the saturation point, then the streamers have a problem.
Amazon says the problem was with something called elastic load balancing services API at a Virginia center. (see history on http://status.aws.amazon.com/?ref_=tsm_1_tw_s_aws_mfk299) Decent article on ELB at http://www.techrepublic.com/blog/datacenter/how-elastic-load-balancing-works-in-amazon-web-services/5381 — seems like voodoo to me.
A woman at MIT says we need to re-engineer the internet to fix this — push content closer to consumers with caches. I thought we did this and called these things content distribution networks.
I’m sure Comcast and FIoS are working on new commercials as I tap out these words. Funny thing is that just a week earlier, this guy was writing about how switching to AWS removed all risk from CDN (http://www.computerworld.in/case-study/how-istream-took-infrastructure-risk-out-equation-cloud-52492012)
Very interesting Len
Got to wonder if Christmas Eve brought millions more viewers looking for the ideal Christmas movie to stream, i.e. saturation as you say.
AWS has all kinds of high profile high security corporate content on it as well. Some businesses are wary of it however fearing they don’t have control of what is in this cloud.
I Hope they figure it out.
Happy New Year