You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Queuing is part of most applications, and it would be awesome if Supabase would provide a native and well-integrated solution. With the current architecture, I would assume that a webhook plugin for realtime would provide such functionality, assuming it can ensure deliverability. There are some discussions around this, and it seems like there has been some work, but I cannot see anything going on lately. A webhook plugin could also be a more scalable approach of triggering an api after something happens in the database compared pg_net.
Main requirements would be
Durable channels that would store the data temporarily and ensure that a client, even if disconnected for a short time, would receive all data sent through the channel
Webhook extension that would send a http request (with proper auth headers) to a specified endpoint when any data is sent through a channel
It seems like there has been some work done a few years back in the context of the workflow RFC, e.g. in #33
Similar features also have been discussed in #66
The text was updated successfully, but these errors were encountered:
Hey,
Queuing is part of most applications, and it would be awesome if Supabase would provide a native and well-integrated solution. With the current architecture, I would assume that a webhook plugin for realtime would provide such functionality, assuming it can ensure deliverability. There are some discussions around this, and it seems like there has been some work, but I cannot see anything going on lately. A webhook plugin could also be a more scalable approach of triggering an api after something happens in the database compared pg_net.
Main requirements would be
It seems like there has been some work done a few years back in the context of the workflow RFC, e.g. in #33
Similar features also have been discussed in #66
The text was updated successfully, but these errors were encountered: