4 ms·
Github had DAYS of an outage because they unsuccessfully tried to scale out SQL rather than dealing with NoSql. There are very few things that structured NoSql
by VirusNewbie 4y ago
Github had DAYS of an outage because they unsuccessfully tried to scale out SQL rather than dealing with NoSql.
There are very few things that structured NoSql can't do if you ignore reporting. Once you scale out traditional SQL, you aren't going to be using it for reporting either way though.
- mh- 4y agoThis is a gross mischaracterization of what caused that outage, even just based on the public information from the (excellent) blog post [0] about it. Automating master failover on MySQL without a human in the loop - in the topology GitHub used back then - is risky. 0: https://github.blog/2018-10-30-oct21-post-incident-analysis/ https://github.blog/2018-10-30-oct21-post-incident-analysis/
- VirusNewbie 4y agoHow is it a gross mischaracterization? You get master master multi regional replication out of the box with cassandra, and github spent an inordinate amount of engineering effort to unsuccessfully slap that on top of MySql.