5 ms·
Grandparent speaks about a different scenario. In a similar vein: imagine your credit card blocks AWS payments, you don't notice, and then AWS payment reminders
by YjSe2GMQ 8y ago
Grandparent speaks about a different scenario. In a similar vein: imagine your credit card blocks AWS payments, you don't notice, and then AWS payment reminders land in your spam folder. Boom, services out.
- eximius 8y agoYea, sure, but you should also consider getting a different credit card AND email provider. Why would a credit card suddenly block charges from a well known company you've been recurring paying for X months or Y years. Why would my email block one of the biggest service providers on the planet?
- rickycook 8y agobecause banks are worse at tech than tech companies if it’s critical, make sure it’s isolated
- Udik 8y agoI think the point is that bank payments, email spam filters, the risk of getting marked as "suspicious activity" as in GP, these become risk factors with a cloud infrastructure as much as, say, a power outage would be if you were self hosting. When you self host something and you have a power outage, that counts as an interruption of service; when a major cloud provider suspends your account because of some chain of mistakes on your or their part, this doesn't impact their SLAs, because the service is technically fine.
- pojzon 8y agoDespite it never happening to me in few years of using AWS, Ill explain the difference between this example and mine. Payment example shows the issue on your end. Something you have control of. In Azure example, companies could do nothing to prevent that outage. Sure you can run services in multiple regions but then you pay absurd amount of money to transfer data between regions (at least in case of AWS).
- madmulita 8y agoIf I'm not mistaken, in Azure's case the issue was with some authentication service that was hosted in only one region but was used by all of them. The service had no redundancy.