Quote:

I am not saying that this architecture is the only viable one, but it does work for TCP for sure (and performs reasonably well too)

Another Quote:

The whole task of optimizing performance beyond, say, 20-50K packets/second per box tends to be Quite Elaborated, and involves quite a few things which are platform- and hardware-dependent.

Quote:

You can still use HLAPI despite its shortcomings

Another Quote:

If you're using one of the engines above (and not your own one), and your game requires Client-Driven Development Flow, you may want to start with a single-player Unity 5, or with a single-player UE4.

Quote:

Modifying generated code usually qualifies as a Really Bad Idea

Another Quote:

How much can be gained by each of such specialized encodings – still depends on the game, but if you can try-and-test a dozen of different encodings within a few hours – it will usually allow you to learn quite a few things about your traffic (and to optimize things both visually and traffic-wise too).

Quote:

In other words, you can write your code 'as if' all-your-code-within-the-same-FSM executed within the same thread

Another Quote:

As soon as we have these two parts of processing – we can say that our Server-to-Server communication is tolerant to all kinds of transient inter-server disconnects