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

System Architecture (and it’s subfield Software Architecture) is a discipline which is surprisingly poorly covered. In a sense, it is still more an art than a science, and usually requires somebody intimately familiar with practical systems, to tell what’s to do and what’s to avoid when building a system.

IT Hares have lots of experience in both Software Architecture and more general System Architecture, and are trying to share their knowledge (and more importantly, their feelings) about them.

All Not so Common Wisdoms about System Architecture, page 7:

Contents of “Development and Deployment of Multiplayer Online Games: from social games to MMOFPS, with stock exchanges in between”

Abstract: There are lots of things to think about when developing a massively multiplayer game
Quote: “Good Development & Deployment cannot make your game, but bad ones can easily kill it”
[]

Multi-threading at Business-logic Level is Considered Harmful

Quote: “However, the window for triviality is very narrow: for example, even going into two interrelated mutexes instead of one, can easily make multi-threading non-trivial”
Another Quote: “Technically you are able to jump to any point of your program, but the variables you see may (and if you have a multi-threaded bug – will) differ every time you jump there.”
[]

Part VIIb: Security (concluded) of 64 Network DO’s and DON’Ts for Multi-Player Game Developers

Quote: “What is practically very important – is to keep all the “unsanitized” data in one place.”
Another Quote: “What will happen if attacker got the whole database of your users’ passwords?”
[]

Part VIIa: Security (TLS/SSL) of 64 Network DO’s and DON’Ts for Multi-Player Game Developers

Quote: “Design of secure protocols is a thing which even security professionals have lots of problems with.”
Another Quote: “In the security field, if you can disable something unused – you SHOULD do it”
[]

Part VI: TCP of 64 Network DO’s and DON’Ts for Multi-Player Game Developers

Quote: “In addition, if TCP_NODELAY is set, it MIGHT help to mitigate consequences of exponential backoff algorithm in case of lost packets.”
Another Quote: “All of us are seeing ‘hung’ HTTP connections on a regular basis – that is, when we’ve clicked a link, and the page loading is stuck forever.”
[]

Part V: UDP of 64 Network DO’s and DON’Ts for Game Engines

Quote: “In general, lag and jitter are not specific to UDP, and manifest themselves for absolutely any Internet connection.”
Another Quote: “If you need a globally-reachable server with single-digit-ms lag for all the players, it is simply not possible”
[]