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
 
“No Bugs” Hare
Author:“No Bugs” Hare  Follow: TwitterFacebook
Species:H.A.R.E. (as "Honest And Restless Engineer")
Job Title:Sarcastic Architect
Hobbies:Thinking Aloud, Arguing with Managers, Annoying HRs,
Calling a Spade a Spade, Keeping Tongue in Cheek
 
'No Bugs' Bunny

Once upon a time, in a rabbit outsourcing warren of Bunnylore, there was a young software developer bunny. And as a developer, he has had one very unusual treat: he was obsessed with eliminating all the bugs he can get his forelegs on. So, it is not surprising that his friends called him a “No Bugs” Bunny (or simply “NoBugs”).

Later on, he grew up, so he decided that “Bunny” in his name has became inappropriate (not to mention potential arguments with Warner Brothers), so he has asked all his friends to call him “No Bugs” Hare. He has made a career as a team lead and software architect, and they lived happily ever after.

“No Bugs” Hare Opera Omnia, Vol.7:

OLTP Database Optimization 102 – DIY Heterogeneous Replication (Part II)

Quote: “The point of Super-Replica is that it is a replica Slave DB which is larger than original Master DB”
Another Quote: “this “don’t write some HISTORICAL data to Master DB” approach can easily allow to reduce the load on the Master OLTP DB by a factor of 2x-3x”
[]

OLTP Optimization 102: DYI Heterogeneous Replication. Part I (Basics)

Quote: “there are still several Big Fat Reasons™ to use DIY replicas”
Another Quote: “With the Replication Messages described above, it is ok to apply Replication Messages to Slave DB which is newer than exactly necessary.”
[]

OLTP DB Optimizations 102 – Group Commits

Quote: “if we can commit several transactions at the same time – RDBMS needs to fsync() our DB logs to physical disks only once”
Another Quote: “if going our preferred way of single-writing-DB connection – make sure NOT to use RDBMS-level Group Commit”
[]

OLTP DB Optimizations 102 –100% Coherent App-Level Cache for Single-writing-DB-connection

Quote: “with our app-level cache, we’re guaranteed to get exactly the same results as if we’d be querying the underlying database.”
Another Quote: “why settle for invalidation when we can modify cache accordingly, saving on the extra DB request when we’re dealing with the same USER again?”
[]