This is pretty interesting as an examination of long polling on the browser as an alternative to websockets. Most of my experience was with it on the backend, e

This is pretty interesting as an examination of long polling on the browser as an alternative to websockets. Most of my experience was with it on the backend, e.g. SQS[1] and hadn't thought much about it beyond, "sit in a loop and check for tasks on a queue." One of the advantages of that approach, I think, was that the queue service is dedicated to just that task so the complexity on that server is all in one place. It would be great if they went into some of the additional architecture they've had to implement to, e.g., prevent denial of service. [1]: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQS...