Supabase said 8k payload limit of listen/ notify is deal breaker for them so they had to start own websocket based realtime engine by watching oplog.
How would you handle that?
We're working on and looking into a few different solutions right now:
1. Split the payload into chunks of 8k bytes and send them as separate messages to the server (in progress, will be released in the next few days).
2. Use a new table as an event queue where the trigger will write data and our server will consume it. We do want to incorporate an event queue soon so this approach would solve for that as long as users are ok with the system writing to a new table.
3. Use one of the Postgres logs to stream events instead of LISTEN/NOTIFY.
Let me know if you have thoughts on any of these approaches!
1. Split the payload into chunks of 8k bytes and send them as separate messages to the server (in progress, will be released in the next few days).
2. Use a new table as an event queue where the trigger will write data and our server will consume it. We do want to incorporate an event queue soon so this approach would solve for that as long as users are ok with the system writing to a new table.
3. Use one of the Postgres logs to stream events instead of LISTEN/NOTIFY.
Let me know if you have thoughts on any of these approaches!