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

Assorted Rants Tagged ‘multiplayer’, page 2:

Preparing to Deploy your Game: To Cloud or Not to Cloud?

Quote: “In fact, the following “hybrid” model is more optimal than both pure cloud-based and pure rental-based ones”
Another Quote: “One relatively recent and certainly welcome addition to the cloud scene, is so-called “bare-metal cloud” servers.”
[]

Production Crashes. Post-factum Debugging. Logging. Replayable Deterministic Re(Actors)

Quote: “I’ve seen game companies with hundreds of thousands of dollars lost per hour of unplanned server downtime.”
Another Quote: “deterministic debugging is by far the best thing I have seen for production debugging.”
[]

(Almost-)Zero-Additional-Latency UDP-over-TCP

Quote: “we realize that for some of the Clients – UDP just doesn’t work because of some weird firewall between Client and Server”
Another Quote: “there is nothing to block us (so head-of-line blocking doesn’t apply)”
[]

TCP Peculiarities as Applied to Games, Part II

Quote: “Nagle’s algorithm aims to deal with those [CENSORED] developers who’re trying to send data over TCP in really small chunks (like 1 byte each time)”
Another Quote: “it seems that “proportional rate reduction” (PRR, reportedly used by Linux kernels by default starting from 3.2) performs for gaming purposes a little bit better than the alternatives”
[]

TCP Peculiarities for Games, part 1

Quote: “the best we can hope when using a single TCP connection over 5%-loss channel – is having 1.5-second “lag spike” every 5 or so minutes, and a 3-second “lag spike” every 2 hours.”
Another Quote: “we may already have the-information-we-need on the receiving host – but this information is hidden from us by layers of abstraction on receiving side”
[]

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