tl;dr - Request that the API support sending outgoing webhooks for ALL Gateway events to reduce Discord + developer hosting costs.
A lot of Discord API functionality for receiving events requires developer applications hold a persistent WebSocket connection. This is labeled as Gateway in the developer documentation. This is costly for both developers and Discord to maintain always-on connections.
This feature request is for Discord to support outgoing webhooks for all Gateway Events. Similar to Interactions, this would allow developers to choose receiving events either by Gateway or outgoing webhook.
This would enable Discord developers to use event-driven, serverless solutions like AWS Lambda, Azure Functions, Google Cloud Functions/Run, etc. Many of these options charge $0 when there are no incoming events (often the case for servers that are dormant during work/school hours).
Example Use Case
My motivating use case is a bot which posts a message when someone joins a voice channel (https://github.com/OliverCardoza/domo). This functionality is not possible without using Gateway events and therefore I need to pay for cloud hosting 24/7 to maintain a WebSocket connection.
If outgoing webhooks were supported I'd be paying a fraction of the cost to only handle 50-100 events a day.
Please sign in to leave a comment.