There's a difference between going offline at a set time for a set amount of time, and going offline randomly for unpredictable amounts of time.
HA is not just about getting that sixth 9, it's also about the peace of mind that you are insulated from a range of problems. Not only would I not worry about our SQL service going down, I also don't have to worry about what I have to do when a node goes down, because that's automated.
Re:Why Does Developing on Kubernetes Suck?
by sametmax on Friday August 23, 2019 @07:48AM
(#20776502)
Even an occasional site crash is ok. I'm not saying it's a good user xp, and avoiding it is both better for the tech team and the marketting one.
But the cost of a 500 is always to be balanced with the cost of going full throttle with micro services.
As perfectionists, it's easy to fall into the trap of choosing the later by default.
What do micro services have to do with it? If anything, HA is harder to achieve with microservices. There's all these weird false dichotomies going around in this thread.
Hell, the stock market goes offline every night.
Those last % of uptime are very, very expensive at every level (money, people, logistic...). They better be worth it.