Best practices / architecture for keeping information live with websockets

[copper ice]

I’m looking into transitioning a static frontend that uses RESTful service to get initial data + websockets to push new data updates to a Next.js site.

I’d like to replace all RESTful requests with server-side rendering, and then after the page is loaded, keep that data up to date with a separate websockets server (not Next).

Trying to understand best architecture for this. How to both pre-render data AND later make it client-side live-updated with websockets and local state.

[tall fable]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)