Realtime & RTK?
I'm an experienced dev and have done projects with web sockets, but I'm getting lost in all the information and misinformation about NextJs (and Vercel hosting)+Supabase+sockets+SWR, etc. My use case is that users can make changes which are batched up and sent to the server. The server takes about 10 seconds to process them. I would like the UI to show a spinner while server is processing then show updated results.
Another section of my app uses Supabase's realtime updates according to a database change. I think piggy-backing off that may make sense. i.e.: when processing starts update status of row to "Processing" which sends real-time to client who starts spinner. When server processing finishes, it updates status of row to "Complete" which sends to client (along with updated results which are stored in the same table) and the client updates its UI.
I am using RTK for other parts of the app, so possibly it makes sense to use RTK streaming updates. If so would that be in addition to the Supabase stuff or instead of? Or maybe using RTK complicates things unnecessarily.
Big picture, because this is hosted in serverless architecture, I think web sockets are ruled out (unless it is done through a persistent side server), which rules out RTK streaming. So the approach is instead a Pub/Sub; which is what the Supabase stuff is. Is that correct?
Another section of my app uses Supabase's realtime updates according to a database change. I think piggy-backing off that may make sense. i.e.: when processing starts update status of row to "Processing" which sends real-time to client who starts spinner. When server processing finishes, it updates status of row to "Complete" which sends to client (along with updated results which are stored in the same table) and the client updates its UI.
I am using RTK for other parts of the app, so possibly it makes sense to use RTK streaming updates. If so would that be in addition to the Supabase stuff or instead of? Or maybe using RTK complicates things unnecessarily.
Big picture, because this is hosted in serverless architecture, I think web sockets are ruled out (unless it is done through a persistent side server), which rules out RTK streaming. So the approach is instead a Pub/Sub; which is what the Supabase stuff is. Is that correct?
