-
Hi, I have an issue with a WebRTC rest API, I can't save in memory few signal bytes of webRTC data because the next peer could not connect to the same instance. Thus leaving two clients connected to 2 different instances for sharing few signal bytes. Please, consider enable again the "scale" limit option or anything to limit instances to just one. Thanks a lot. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Serverless Functions are a completely different concept than v1 containers, so the same command and concepts like manual scaling can't be carried over. The concurrency for functions are handled automatically and if an endpoint is hit at the same time by other users, a new function will serve the second request without any shared state. Serverless Functions may not be the best solution for your WebRTC backend server. |
Beta Was this translation helpful? Give feedback.
Serverless Functions are a completely different concept than v1 containers, so the same command and concepts like manual scaling can't be carried over.
The concurrency for functions are handled automatically and if an endpoint is hit at the same time by other users, a new function will serve the second request without any shared state.
Serverless Functions may not be the best solution for your WebRTC backend server.