Scale Plan

[Jared-Sprague]

• [x] Figure out how much capacity 1 linode can handle of real websocket clients
• [x] Figure out how to proxy a websocket connection from a client though the NodeBlancer to one of multiple zorbio instance running on the linode
• [x] possible to auto assign which NodeBalancer based on client geo
• [x] Automate adding more linodes to NodeBalancer that can accept game connections to multiple nodejs instances instantly
• [x] Automate weighting nodes that are full
• [x] Automate re-adding nodes that are out of rotation when space opens up
• [x] Notify when balancer full or idle
• [x] Test scale simulation

[Jared-Sprague]

Ok I did some simple websocket benchmarking with https://github.com/observing/thor, and once it get's past 100 connections it starts to get slow and fail. I think we should start with 90 web socket connections per server. So that could be three game instances of 30 players each per server.

[Jared-Sprague]

Infrastructure:

[Jared-Sprague]

Node architecture:

[Jared-Sprague]