Server side rendering of "private" pages is seriously overrated.
I can understand server-rendering (with data) a public "feed" when you are a huge site, and you are using user-generated content or product listings to sell a new visitor on the idea of your service.
But for everyone else, statically rendering a pretty home page (with login at the top or middle) is plenty, since you can preload the next bundle you need while the user completes this task.
Building a greenfield "front end server application" that actually uses the user session to fetch private data from "isomorphic data sources" is massive overengineering.
If you are so concerned with the "first load after update" of already-logged-in users, just code-split better. Serverside rendering isn't "a solution" to the fact you are sending your user 100MB of text as many times per day as you push to master to look at one route they keep open in a tab somewhere.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Server side rendering of "private" pages is seriously overrated.
I can understand server-rendering (with data) a public "feed" when you are a huge site, and you are using user-generated content or product listings to sell a new visitor on the idea of your service.
But for everyone else, statically rendering a pretty home page (with login at the top or middle) is plenty, since you can preload the next bundle you need while the user completes this task.
Building a greenfield "front end server application" that actually uses the user session to fetch private data from "isomorphic data sources" is massive overengineering.
If you are so concerned with the "first load after update" of already-logged-in users, just code-split better. Serverside rendering isn't "a solution" to the fact you are sending your user 100MB of text as many times per day as you push to master to look at one route they keep open in a tab somewhere.