Scaling system

[yeslayla]

This could probably be a project within itself. The following tasks need to be done:

• Scaling policies
• Dynamic player management
• Stateless servers
• CloudWatch PlayerCount
• ECS & ECS Scaling Policies

[yeslayla]

Okay, so after a little bit of research and thought experiments it looks like I will need two servers:

Authorizer

Sort of a middle man TCP server that connects clients to servers. Will use redis for storing caching data and scalability.

Functions

• Login system to generate tokens
• Tell clients which server they should connect to
• Tell servers which clients they should have
• Tell servers what data they are in charge of
• Tell clients to change server in case of:
  • Dead node
  • Player location changes to data owned by different node

Node

The node will be the actual game server. It manages the data given to it by the client.

May use redis?

Functions

• Game logic
• Controls, entities, tiles, and players within it's data set
• Verifies authorized connections

---

Next step here would be to create a project board for this major feature.

[yeslayla]

Current progress:

• [x] Redis cluster
• [x] Basic TCP server (C#)

Dev branch: feature/scaling