RFC 0017 - Introducing a new EventSub transport type: Conduit

I’m curious about this part - above, it is mentioned

but a “minimum” would discourage developers from using a conduit if all they need is a WebSocket connection in a firewalled server scenario, where webhooks are unavailable and User Access Tokens are not wanted, whilst being on low enough volume (or the existing infrastructure only) warrants no more than a single connection on a single thread.

Whichever arbitrary non-singular minimum is chosen, it would force developers to have a minimum scale active at any given time, effectively removing the benefit of being able to scale-down when no traffic is expected/no capacity is needed.

As active example, I can quote my own bot, which never exceeds over 50 Events per second, and the average is below 1 per second. I do not require multiple connections. I just want WebSocket on the Server side.

2 Likes