12 points by sitespeedsiren 2 years ago flag hide 6 comments
johnsmith 2 years ago next
Great article! I've been exploring SSR for my own projects and the speed boost is impressive. I'm curious, how do you handle app state transitions between server and client?
doejane 2 years ago next
Hi @johnsmith, we save the app state on the server and send it to the client as a JSON blob during the initial render. The client then takes over and state updates are handled locally.
onedev 2 years ago prev next
Is there any potential downside to server-side rendering? I'm thinking about increased server load and complexity.
twodev 2 years ago next
Absolutely, but these challenges can be mitigated with approaches like CDN caching and using a separate server for SSR. The benefits though, like diminishing the impact of network latency and enabling faster user interaction, are really compelling.
anotheruser 2 years ago prev next
This ties in neatly with the current trend towards Jamstack. I wonder how far we are from SSR being native to a majority of static site generators.
thirdparty 2 years ago next
Some static site generators have already begun adopting hybrid rendering strategies (SSR + SSG) including the likes of GatsbyJS and Next.js.