Server isolates cause Socket.IO problems
Hi guys,
I have a simple socket.IO program that basically broadcasts the changes in any one client's input field to every other client's input field. But I've seen that since Deno Deploy runs the different servers on the edge, different socket.IO servers are run for users from different locations.
This means that eg. someone sitting in Asia and making a change won't affect the input of someone sitting in Europe.
I believe a solution to this would be to use Deno KV or some other database to store the changes globally, but that would introduce delays that defeat the whole purpose of realtime communication.
What other solutions would you recommend? Is there any configuration on Deno Deploy or socket.IO that fixes this?
Thanks!
I have a simple socket.IO program that basically broadcasts the changes in any one client's input field to every other client's input field. But I've seen that since Deno Deploy runs the different servers on the edge, different socket.IO servers are run for users from different locations.
This means that eg. someone sitting in Asia and making a change won't affect the input of someone sitting in Europe.
I believe a solution to this would be to use Deno KV or some other database to store the changes globally, but that would introduce delays that defeat the whole purpose of realtime communication.
What other solutions would you recommend? Is there any configuration on Deno Deploy or socket.IO that fixes this?
Thanks!
