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. 2 (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.2 (1st beta), page 1:

Packet Loss for an App-Level Developer. Part II. Last Mile, Wi-Fi, and Summary

Quote: “Burstable packet loss. May be caused by a neighbor preparing his breakfast”
Another Quote: “if there is a NAT device on the way from your Client to your Server – a sudden IP change can occur with absolutely no notification to Client whatsoever.”
[]

Packet Loss for an App-Level Developer. Part I. Router Failures, BGP Convergence Time, AQM, Traffic Shapers.

Quote: “All the routers, switches (actually – pretty much each and every device which forms Internet infrastructure) – are allowed to drop each and every packet.”
Another Quote: “TCP, when it observes a dropped packet, interprets it as an indication of congestion – and slows down.”
[]

Indirect and Client-Centric Payment Processing. Logging and Reconciliation

Quote: “Fortunately, there is a neat crypto-trick which makes this schema usable for Server-oriented games in general – and multi-player games in particular”
Another Quote: “if you’re using TCP to communicate, you should log everything right before it goes into your send() call (and right after it comes out of your recv() call”
[]

Direct Payment Processing. Recovery from ‘Unknown’ Transaction Status. PCI DSS.

Quote: “With the Direct Processing, customer should trust us (the merchant) with their details”
Another Quote: “On the other hand, most of PCI DSS requirements make perfect sense regardless of formal compliance”
[]

Payment Processing. Credit Cards. Chargebacks and Collateral Damage

Quote: “Chargeback monster will come from under the bed and will eat all your hard-earned money!”
Another Quote: “it is trivial to develop a system with guaranteed zero chargeback rate – to achieve this, it is sufficient to decline each and every transaction at pre-filter stage”
[]

Gradual OLTP DB Development – from Zero to 10 Billion Transactions per Year and Beyond

Quote: “to make an efficient representation usable for OLAP – we need to modify our data on its way to OLAP replicas”
Another Quote: “Each of the DB Server Apps is a replica master, but all replica targets are within the same Replica DB”
[]

Representing The Same Data Structure in SQL and NoSQL (from Classical Codd-style SQL to Key-Value NoSQL with SQL-with-XML and Structured NoSQL in between)

Quote: “while duplication MAY indeed improve performance – undue duplication also MAY hit performance pretty badly”
Another Quote: “NoSQL will usually call for another denormalisation on top of what we’ve described above for SQL-with-XML.”
[]