Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 5
    the reason people like to ask this question is that it breaks the web paradigm of request and response. But really websockets has been a thing for a while now and anyone who has played a multiplayer game in the last 20 years is unsurprised that you can see what others are doing to a document Commented Sep 13, 2021 at 17:26
  • @DanWilson Could you please elaborate? How would those messages be partitioned, and how would the hub be scaled between multiple nodes? Commented Sep 13, 2021 at 20:41
  • @Ewan My question is not whether it's technically possible, how to do it quickly and efficiently at scale, because for only thousands of concurrent users and hundreds of documents this is a no-problem. Could you elaborate on your comment? Commented Sep 14, 2021 at 6:27
  • "Running the changes through a single message queue and processing it on each node to notify users connected to node" Why a single queue and not a topic per document? Commented Sep 14, 2021 at 15:54
  • @sdds when modern games easily handle 64 players all jumping around and shooting each other in real time with millisecond response times, why is have doc edits for 100 people and sub second response times considered a problem? Your naive approach with a queue and web-sockets is pretty much going to work Commented Sep 14, 2021 at 17:12