Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.
We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.
What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.
Your mileage may vary. Batteries not included.
Ultimate DB Heresy: Single Writing DB Connection. Part II. Gradual Scalability. All the way from no-scale to perfect-scale.
November 7, 2016 by • “No Bugs” Bunny
Quote:
And after this split of USERS table, the system has achieved perfectly linear scalability.
Another Quote:
Start with a simple single-write-connection DB, with reporting running off the same DB
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions(Re)Actors
Read moreUltimate DB Heresy: Single Modifying DB Connection. Part I. Performance (Part II. Scalability to follow)
October 31, 2016 by • “No Bugs” Bunny
Quote:
Dealing with transaction isolation is very far from being a picnic
Another Quote:
One of such real-world systems was consistently processing over 30M real-world write transactions/day over one single DB connection, supporting ~100K simultaneous players.
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions(Re)Actors
Read moreNoSQL vs SQL for MOGs
October 24, 2016 by • “No Bugs” Bunny
Quote:
in real world, after deployment, most of the changes in DB structure are about widening columns and adding the new ones
Another Quote:
For documents and BLOBs, NoSQL is a natural habitat
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions
Read moreDistributed Databases 101: CAP, BASE, and Replication
October 17, 2016 by • “No Bugs” Bunny
Quote:
The worst case of inconsistency happens when row X in database A is modified (by a Client connected to datacenter A), and the same row X in database B is independently modified too (by a Client connected to datacenter B).
Another Quote:
One way to avoid reports affecting operational DB, is via creating a read-only replica of our main operational DB – and running our reports off that replica.
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions
Read more



