6 ms·
I wonder what game this was for. To me this is validation that going the SQL route in almost 99% of new apps is the right way to go. It will be a rare case tha
by jtchang 3y ago
I wonder what game this was for.
To me this is validation that going the SQL route in almost 99% of new apps is the right way to go. It will be a rare case that you won't be able to scale out given how mature some of these technologies are.
- chrismsimpson 3y agoMongoDB ftw. Even has graph capabilities.
- VectorLock 3y agoIts web scale!
- chillydawg 3y agoDemonware handle the online services for the CoD franchise.
- ultrahax 3y agoThey handle online services for pretty much any Activision-published game, with carve-outs for Blizzard and King - they still do most of their own backend stuff themselves, with some collaborations.
- VirusNewbie 3y agoGithub 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- 3y 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 3y 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.