Re:Postmortem of database outage of January 31
by bitshepherd on Friday February 10, 2017 @07:20PM
(#13620125)
A great number of issues can be attributed to the selection of Azure as the platform of choice. That said, a little bird told me that the decision was largely a cost factor. "You get what you pay for" never rang more true.
[ Parent
| on HN ]
Re:Postmortem of database outage of January 31
by tedunangst on Friday February 10, 2017 @07:45PM
(#13620226)
But none of the issues were azure/cost related except for the slow recovery? I mean, neither AWS nor GCE can make you notice youre not getting cron mail.
Re:Postmortem of database outage of January 31
by teej on Friday February 10, 2017 @07:56PM
(#13620283)
Setup a cloudwatch alarm and have cron send a keepalive email to it..? Without looking, I'm pretty sure that does exactly what you want.
Re:Postmortem of database outage of January 31
by tedunangst on Friday February 10, 2017 @08:00PM
(#13620302)
And also entirely possible to do with azure. AWS doesn't make you do that.
Also, depending on precise nature of the dmarc fuckup, wouldn't help anyway. Cloud watch receiving mail doesn't guarantee that you will receive mail.
Re:Postmortem of database outage of January 31
by ronack on Friday February 10, 2017 @09:18PM
(#13620566)
Yes, I recall seeing a ticket that referenced Gitlab using Azure because it was heavily subsidized. My company uses Azure for much the same reason, and my experience has been largely positive.