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 8:

Part IV: Great TCP-vs-UDP Debate of 64 Network DO’s and DONT’s for Game Engines

Quote: ““Why bother with UDP at all? The answer is simple: there is a price tag attached to the TCP goodies.”
Another Quote: ““Implementing your own reliable-delivery protocol over UDP is extremely complicated, time-consuming, and error-prone.”
[]

Part IIIb: Server-Side (deployment, optimizations, and testing) of 64 Network DO’s and DONT’s for Game Engines

Quote: “If your game is the only one working when all the competition is down, it improves user perception about your app a lot.”
Another Quote: “Most importantly, however, this approach allows to keep your players happy – and this is one thing which really matters”
[]

Part IIb: Protocols and APIs (continued) of 64 Network DO’s and DON’Ts for Game Engine Developers

Quote: “You shouldn’t count on outsmarting all those millions of highly motivated hackers operating in an environment under their own control.”
Another Quote: “Burst consisting of several million packets, may start causing observable issues for a mid-size ISP.”
[]

Part IIa: Protocols and APIs of 64 Network DO’s and DON’Ts for Game Engine Developers

Quote: “While using framework is fine, forgetting about it is not.”
Another Quote: “Even if you’re forcing the auto-update every time the game app starts, there still are users who were online at the moment of the update, and those who found a way to bypass game updates”
[]