Laravel Reverb Redis Channel Manager

[joekaram]

Hello,

I'm planning to use Reverb for a large-scale project that I'm working on: thousands of concurrent connections and ~5k messages every 5 seconds, at a constant rate. That said, I will definitely have multiple Reverb servers behind a proxy, so Reverb scaling is enabled.

To broadcast events, I have extended the Pusher broadcaster to create a custom one. I'm now bypassing the HTTP web server, and directly publishing events to Redis. That can be a separate discussion for later, and potentially a new broadcasting driver/connection.

I'm starting this discussion to check if it's a good idea to create a Redis channel Manager, to use instead of the array channel manager. All connections, of all servers, would be stored there. Are there any limitations to such approach?

The reason I need it to be shared is to access the channel manager, from another process, and determine which channels have active connections. This way, I would not publish messages to Redis if there are no clients connected to the destination channel, thus reducing the number of messages.

If someone's already working on such functionality, please reach out, I would be happy to collaborate.

Thanks!!