3 ms·
> available 99.5% of the time with decent alerting for operators to kick it An operator should never have to "kick" a service. It should repair itself, except
by mwcampbell 8y ago
> available 99.5% of the time with decent alerting for operators to kick it
An operator should never have to "kick" a service. It should repair itself, except for the occasional hardware replacement if one is working with bare metal. And for anything that's being sold as a product, as opposed to an internal tool, I think 99.9% availability should be the minimum.
But I don't know enough about Kubernetes to say whether it's overkill at the scale of just a few servers.
- 49bc 8y agoHow many “kicks” does it take to build a reasonably resilient distributed service? A lot!
- wang_li 8y agoCAP theorem says it's impossible.
- Xorlev 8y agoThat isn't what the CAP theorem says at all. It says you need to pick your guarantees. Additionally, resilience is in the eye of the beholder: might mean AP for a service that needs to be up at the cost of consistency or CP for a service that detects when it can't achieve quorum and fail gratefully.
- smudgymcscmudge 8y ago> An operator should never have to "kick" a service. Have you ever been a sysadmin? There are very few services that don’t need a kick every now and then.
- mwcampbell 8y agoYes I have. And if a service ever needs a manual kick, I consider that a bug. At least when running in a public cloud.
- randallsquared 8y agoSure, sure, but... everything is buggy, by that metric. I think that's what the parent comment was getting at.