> being on the cloud means downtime is correlated with downtime of other services. That's usually a good thing. A long time ago, I used to circulate snarky lit

> being on the cloud means downtime is correlated with downtime of other services. That's usually a good thing. A long time ago, I used to circulate snarky little emails at work. One of them was responding to this very concept. My managers were throwing out our working and mature UNIX servers (implementing DNS, Mail, and other services) in favour of NT. The new system crashed a lot, we had some security breaches, but at least it was 'industry standard.' Managements' response was that with the UNIX stuff we had no one to pin our outages on. Now we could blame Microsoft, and call their support line. I circulated an email making fun of this justification, which promoted a fictional product called 'Blame Studio' which would help you map out the blame path for any of your products or services. It would help to make sure that none of the blame ever landed on you, but rather was always redirected onto some other company.