[blensor]

Lambda has currently a limit of 15 minutes as far as I can remember. I was considering it for a very cost efficient way to scale our multiplayer backend in VRWorkout (dynamically spin up room servers as needed) since it all fits in a single python module. But with the 15 minute limit it's not an option.

I would not even need data syncing since it talks to the main server and does not have state. But it would need to be reachable on a public IP

[ainzzorl]

Lambda indeed is not the right tool for this. It sounds like you need some infra that can auto scale - there are many ways to do it on AWS (EC2 auto scaling, ECS, EKS), any other cloud provider, with Kubernetes...

[blensor]

yes, probably, but then we are back where I need to put a lot more effort into it than I wanted to at this stage.

I really only need to cover burst usage since an average VRWorkout session is only ~10-20 minutes anyway and with players being distributed around the world there is usually no need to boost the available resources.

That's a problem I would like to have down the road when we have millions of people doing VR fitness though :)