Work/life balance is a false dichotomy. In the ideal world, one's work is one's life, and conversely, one's life is one's work. But that's a discussion for another time.
I was merely commenting on the fact that whomever was on call tonight (I know an SRE @ Google as well) probably had a stressful experience. I hope there is a post-mortem, as I'm sure many of us could learn from such an event as the one that transpired earlier.
Well, actually I disagree with this statement completely, I recommend you reading "In Praise of Idleness" from Bertrand Russell if you've never read it, it's a good point of view on how "leisure time" not necessarily needs to be productive to be enjoyable.
I find it rather odd to have a GLOBAL 500 even for a minute (it may be still lasting at least in some regions http://downdetector.com/status/youtube) when a web app is distributed among servers, services, dockers or whatever and has so many systems in place to roll back automatically.
35 comments
[ 3.6 ms ] story [ 65.6 ms ] threadedit: available again.
I was merely commenting on the fact that whomever was on call tonight (I know an SRE @ Google as well) probably had a stressful experience. I hope there is a post-mortem, as I'm sure many of us could learn from such an event as the one that transpired earlier.
The same thing happened about a week ago with Fb Messenger (http://downdetector.com/status/facebook/news/53463-problems-...).
I expect this level of outages in 2016 to be only caused by solar flares, am I missing something?
Absolutely. Just to name a few:
Deploys. Migrations. 3rd Party Systems. Configuration Rollouts. Failover not happening. Accidental failover. Rogue Employees. Routing changes.
oh yes, Solar Flares too, but they're rather the exception.
"Did I just accidentally reboot every webapp server for the entire site!? I hope nobody notices."