Readit Newshttp://www.askamanager.org/2016/10/update-a-coworker-stole-m...
I would argue that bandwidth-sharing fairness with stuff going over UDP is easy: Just start dropping packets when pipes get full.
Most updates are going to be pretty small. It's not like game developers want the user experience of their titles to be bad, after all.
You’re not consindering a server, the bandwidth is very high on the backend and does saturate links. You run many servers per physical or virtual machine due to cost, so you can have 1000s if players connected over a single network path.
Deleted Comment
You can drain stuff by changing a Service's selector but leaving the Deployment alone. Instead of changing a Deployment and doing a rolling update, create a new deployment and repoint the Service. Existing connections will remain until you delete the underlying Deployment.
At some point Microsoft told me I had to change my password for Skype. The "Reset your password" process failed 6 times in a row. I eventually had to create a new, Microsoft ID, to use Skype. I lost all of my old contacts and had to slowly recreate my address book. This is really one of the worst transitions I can recall.
Meanwhile, I act as adviser to a number of entrepreneurs, and the biggest trend of the last year has been "I want to do _______ for professionals, since LinkedIn isn't doing it." The lost opportunities for LinkedIn are very sad.
And combining that data with LinkedIn’s data would be valuable indeed.