-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy on AWS with Lambda #7
Comments
Absolutely, however in case of this example to work there, singling server would need to be updated a little bit, to meet requirements of AWS Lambda and API Gateway. The state has to be persisted somewhere, in a database, so you can track each of the connected clients. https://aws.amazon.com/blogs/compute/announcing-websocket-apis-in-amazon-api-gateway/
|
Thank you very much for the info Rafal. And appart from Lambda, API Gateway, RDS database (or SNS) we do not need any streaming server in the middle because it is peer to peer right? |
Yes, the only thing you need is a signalling server (in this case it would be API Gateway) |
I set up some simple explanation how you can implement your own signaling channel let me know if it need improvements |
Is it possible to deploy it to AWS with Lambda and API Gateway?
The text was updated successfully, but these errors were encountered: