If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

This category consists of posts which form “1st beta” of the Vol. IV-VI (Development) of the upcoming 3-volume monster “Development & Deployment of Multiplayer Online Games”. Please note that order of the posts is “as they were published on this site”, and is not exactly the same as the order of the Chapters within Vol. 2. For Chapters in correct order – please refer to ToC of Vol. 2.

D&D of MOGs: Vol. IV-VI (1st beta), page 3:

OLTP. Compiling SQL Bindings.

Quote: “If we’re speaking about millions transactions per day over just a few hundred of different SQL statements – compiling those statements a million times (instead of a few hundred times) will be a dramatic waste of resources.”
Another Quote: “Once upon a time, I observed the largest C++ file in my career – it was a 30’000-line file(!) consisting merely of ODBC bindings (and that was just for 300 or so SQL statements)”
[]

Historical Data in Databases. Audit Tables. Event Sourcing

Quote: “99% of reporting requests and 99.9% of analytics is purely historical”
Another Quote: “Information within the audit table should be sufficient to validate/justify current state”
[]

Ultimate DB Heresy: Single Writing DB Connection. Part II. Gradual Scalability. All the way from no-scale to perfect-scale.

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”
[]

Ultimate DB Heresy: Single Modifying DB Connection. Part I. Performance (Part II. Scalability to follow)

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.”
[]

Distributed Databases 101: CAP, BASE, and Replication

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.”
[]