Re:How we migrated onto K8s in less than 12 months
by zelphirkalt on Friday August 09, 2024 @06:46AM
(#41200563)
That's really a too broad generalization.
Services that people might leave, because of downtime are for example a git hoster, or a password manager. When people cannot push their commits and this happens multiple times, they may leave for another git hoster. I have seen this very example when gitlab was less stable and often unreachable for a few minutes. When people need some credentials, but cannot reach their online password manager, they cannot work. They cannot trust that service to be available in critical moments. Not being able to access your credentials leaves a very bad impression. Some will look for more reliable ways of storing their credentials.
Re:How we migrated onto K8s in less than 12 months
by Bjartr on Friday August 09, 2024 @08:15AM
(#41201073)
The user experience of "often unreachable" means way more than 3m per week in practice.
Re:How we migrated onto K8s in less than 12 months
by skydhash on Friday August 09, 2024 @11:37AM
(#41202888)
Why does a password manager needs to be online. I understand the need for synchronization, but being exclusively online is a very bad decision. And git synchronization is basically ssh, and if you mess that up on a regular basis, you have no job being in business in the first place. These are examples, but there's a few things that do not need to be online unless your computer is a thin client or you don't trust it at all.
That's still a business decision.
Customers don't vote with their feet based on what tech stack the business chose, they vote based on a range of other factors, few, if none, of which are related to 3m of downtime.
There are little to no services I know off that would lose customers over 3m of downtime per week.
IOW, 3m of downtime is mostly an imaginary problem.