3 ms·
Both of the services you mentioned have had major outages in the past. Maybe it’ll never happen again, but your customers don’t want to hear about why they can’
by aidos 6y ago
Both of the services you mentioned have had major outages in the past. Maybe it’ll never happen again, but your customers don’t want to hear about why they can’t currently do business because some service they don’t even know about, in which you’re hosting their data, isn’t working.
As ever, there are trade offs and you take the good with the bad.
- sixstringtheory 6y agoOutages occur all the time. What difference does it make where exactly they're originating from if the end result is the same, from the end user's POV? You give them the same message in either case: "we're experiencing a temporary outage and are working on a remediation." I suppose you'll also be compensated according to contract SLAs, and if the hypothetical becomes actual, you can tune your contract renewal based on your observed losses in revenue accordingly. Best case scenario, there's healthy competition in the space, providing more alternatives and allowing you to end your contract with them if the service sucks. Worst case scenario I guess is that the company implodes taking all its data with it, affecting untold amounts of businesses. A GDPR-like regulation stipulating the ability to export that data (so, user databases) would go a long way towards mitigating prolonged outages in that worst case, and in the best case of the worst case, their competitors are able to import the exports. And/or tools that can spin up a $database instance in $cloud.