Re:Debian Handbook for Debian 10 Buster
by ploxiln on Monday June 01, 2020 @06:29PM
(#23384782)
I think a lot of devs and organizations these days take the "cattle" idea too far, to the point they're like industrial factory farms where all the animals are sickly, and the pools of effluent occasionally break out of containment and kill everything in the local watershed. Yeah, cattle, sometimes servers die and you replace them. But these organizations get too accustomed to just re-launching a whole new autoscaling group because the old one went bad for some reason that no one really wants to figure out. I get the impression they don't realize how unusual it is for a quarter of the cattle to die in a week. Meanwhile, my 100 or so "pets" are managed using an appropriate level of automation and monitoring, and I get a random bad-hardware incident about every 6 months. Compare that to monthly whole-cluster outages from the full-best-practices all-cattle people.
[ Parent
| on HN ]
Re:Debian Handbook for Debian 10 Buster
by moreaccountspls on Monday June 01, 2020 @06:52PM
(#23385017)
> Compare that to monthly whole-cluster outages from the full-best-practices all-cattle people.
I'm trying to phrase this as nicely as I can: this statement does not reflect the reality of modern day operations.
edit: For people downvoting
1) How exactly do you think operations at companies like Google, Facebook, Amazon, Netflix, Uber, Spotify, etc. work?
2) How often are those companies having monthly outages?
Well at a low level we all know that AWS works akin to a Rube Goldberg machine, where a failure in some forcibly dogfooded service means even their own fucking status page can’t be updated, not to mention the dozens of seemingly unrelated services that suddenly don’t work.
HN is weirdly hostile towards the modern distributed systems and DevOps ideologies. The amount of people making incorrect opinions on K8s threads is just staggering for a technically inclined crowd.