IT Hare on Soft.ware
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

Wikipedia defines a distributed system as a “software system in which components located on networked computers communicate and coordinate their actions by passing messages.”

In modern world, more and more systems become distributed. Yet, surprisingly few authors write about practical architecture of distributed systems. As our Hare have architected all kinds of distributed systems, from a stock exchange to a billion-messages-a-day game, we’re in a very good position to fill this gap.

Distributed Systems, page 4:

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

posted by

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

posted by

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”
[→]
Copyright © 2014-2016 ITHare.com