pubsub-benchmark VS geckos.io

Less of a note on scale and more of a note on websocket tools/abstraction - I was building something similar for an internal tool at work (locally hosted on our server, not on AWS, but very high bandwidth use for client programs). In my application for it, there were a lot of intermediate steps need for Socket.io in comparison to SocketCluster. Additionally, SocketCluster was a little more efficient hardware-wise. This link is a little outdated, but I found similar results when testing myself. That being said, as always, use what works for you!

First, I would try exchange Socket.io over Geckos - https://github.com/geckosio/geckos.io.

I agree the scope is massive. I think a lot of people struggle with figuring out how to even get started with multiplayer dev, and I hope Hathora can be a useful tool for them.

Thanks for linking matchbox - I've been looking into https://github.com/geckosio/geckos.io as a way to integrate WebRTC into Hathora

https://github.com/pion/datachannel looks great! Thank you for sharing your project with the open source community.

I just starred it, it does seem like it'd alleviate a some of the pain. Another similar (more end to end) project I had come across is: geckos.io. This previous HN thread[1] discusses some of the (at least perceived) difficulty with using WebRTC as a "WebSockets but UDP" solution.

I'm not sure I follow the concern about congestion control. UDP doesn't have it either, presumably since if you're building an application that requires such latency sensitivity, you don't mind rolling your own congestion control algorithm that makes most sense given your application's specific needs, right? Pretty much all FPS games do this, as far as I understand.

[0] https://github.com/geckosio/geckos.io