This is likely a non-code change, although #28 would likely be a prerequisite.
To enable having a larger userbase, it would make sense to separate hosting for cloud and services, and provide load balancing for services where possible. It is likely we could take advantage of the tools provided by AWS.
It also might be possible to have routing based on specific services/calls based on statefulness. Some highly-stateful services (e.g. IoTScape and RoboScape) may need to have a single instance shared by all users.
Ideally, this would make "services.netsblox.org" connect your session to the least used of a set of servers. Autoscaling would also make a lot of sense, the demand for services changes significantly during the day.
This could also allow for services to be hosted in multiple regions for faster access to users not in the eastern US.
This is likely a non-code change, although #28 would likely be a prerequisite.
To enable having a larger userbase, it would make sense to separate hosting for cloud and services, and provide load balancing for services where possible. It is likely we could take advantage of the tools provided by AWS.
It also might be possible to have routing based on specific services/calls based on statefulness. Some highly-stateful services (e.g. IoTScape and RoboScape) may need to have a single instance shared by all users.
Ideally, this would make "services.netsblox.org" connect your session to the least used of a set of servers. Autoscaling would also make a lot of sense, the demand for services changes significantly during the day.
This could also allow for services to be hosted in multiple regions for faster access to users not in the eastern US.