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 upcoming book “Development & Deployment of Multiplayer Online Games”. Please note that “2nd beta” (available on Indiegogo) has 75% of the new content compared to the “1st beta” (in particular, based on the comments here on ithare.com and on /r/programming), so please don’t hit me too hard for the quality of the “1st beta”. ToC of “2nd beta”.

D&D of MOGs: Vol.1 (1st beta), page 2:

Asynchronous Processing for Finite State Machines/Actors: from plain event processing to Futures (with OO and Lambda Call Pyramids in between)

Quote: “With ‘callback pyramid’ it is not easy to express the concept of ‘wait for more than one thing to complete’ , which leads to unnecessary sequencing, adding to latencies (which may or may not be a problem for your purposes, but still a thing to keep in mind).”
Another Quote: “Don’t even think of converting all of your code to a so-called Continuation-Passing-Style”

MMOG Server-Side. Eternal Linux-vs-Windows Debate

Quote: “Each server is only as secure as its admin”
Another Quote: “For cheaper servers, the difference between Windows and Linux can eat as much as 50% of the server rental price (though for those servers which are more or less optimal price-performance-wise observed difference was closer to 20-30%).”

Chapter VI(b). Server-Side Architecture. Front-End Servers and Client-Side Random Load Balancing

Quote: “[about Round-Robin DNS] one of these returned IPs can get cached by a Big Fat DNS server, and then get distributed to many thousands of clients”
Another Quote: “As a rule of thumb, Front-End Servers are a Good Thing™”

Chapter VI(a). Server-Side MMO Architecture. Naïve, Web-Based, and Classical Deployment Architectures

Quote: “If you disrupt the game-event-currently-in-progress for more than 0.5-2 minutes, for almost-any synchronous multi-player game you won’t be able to get the same players back, and will need to rollback the game event anyway.”
Another Quote: “However, keep in mind, that all fall-tolerant solutions are complicated, costly, and for the games realm I generally consider them as an over-engineering (even by my standards).”

Chapter V(d). Modular Architecture: Client-Side. Client Architecture Diagram, Threads, and Game Loop

Quote: “To have a good concurrency model, it is not strictly necessary to program in Erlang”
Another Quote: “Most of developers agree that FSM-based programming is beneficial in the medium- to long-run.”

Chapter V(c). Modular Architecture: Client-Side. On Debugging Distributed Systems, Deterministic Logic, and Finite State Machines

Quote: “After your logic has failed in production, you can “replay” this inputs-log on your functionally identical in-house system, and the bug will be reproduced at the very same point where it has originally happened.”
Another Quote: “You can implement your Finite State Machine as a deterministic variation of a usual event-driven program”

Chapter V(b). Modular Architecture: Client-Side. Programming Languages for Games, including Resilience to Reverse Engineering and Portability

Quote: “from all the popular compiled languages, C++ tends to produce the binary code which is the most difficult-to-reverse-engineer (that is, provided that you have turned all the optimizations on, disabled debug info, and are not using DLLs)”
Another Quote: “Bot fighting is always a two-way battle with bot writers inventing a way around the MMO defences, and then MMO developers striking back with a new defence against the most recent attack; rinse and repeat.”