so if "Although good for specific use cases, it isn’t a silver bullet for real-time communication."
what is the silver bullet (the best solution for real time communication) ?
If google docs uses websockets - how does google docs handle the server limited websocket connections issue?
> what is the silver bullet (the best solution for real time communication)?
it depends.
> If google docs uses websockets - how does google docs handle the server limited websocket connections issue?
I'll have to find out how Google Docs scale websockets. (They have less information in the public domain.)
Here are 2 approaches:
- Vertically scale the server to handle more connections.
- Add more servers to scale horizontally and put a load balancer in front of them.
You can use the pub-sub pattern to handle many websocket handshake requests at once. It uses a message broker to shed the load.
undefined subscriptions will be displayed on your profile (edit)
Skip for now
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to sign in.
so if "Although good for specific use cases, it isn’t a silver bullet for real-time communication."
what is the silver bullet (the best solution for real time communication) ?
If google docs uses websockets - how does google docs handle the server limited websocket connections issue?
> what is the silver bullet (the best solution for real time communication)?
it depends.
> If google docs uses websockets - how does google docs handle the server limited websocket connections issue?
I'll have to find out how Google Docs scale websockets. (They have less information in the public domain.)
Here are 2 approaches:
- Vertically scale the server to handle more connections.
- Add more servers to scale horizontally and put a load balancer in front of them.
You can use the pub-sub pattern to handle many websocket handshake requests at once. It uses a message broker to shed the load.