SSR benefits
Unanswered
Siamese Crocodile posted this in #help-forum
Siamese CrocodileOP
Can someone explain some solid reasons why it makes sense to use SSR for user-specific or request-related pages like account settings?
Even when using PPR, is there really a difference between showing a loader and fetching the data on the client vs. using suspense, fetching the data on the server, and streaming the response?
(Obviously, I'm talking about using a separate API and not calling the database directly from a server component.)
Because honestly, I don’t see the difference or benefits here.
What I do see are a lot of problems—mainly around using Next.js and an API layer that seems to change with every new framework version 😛
In general, I see a lot of benefits in using SSG or ISR, but I don’t really see any for SSR where the page is rendered on every request.
Even when using PPR, is there really a difference between showing a loader and fetching the data on the client vs. using suspense, fetching the data on the server, and streaming the response?
(Obviously, I'm talking about using a separate API and not calling the database directly from a server component.)
Because honestly, I don’t see the difference or benefits here.
What I do see are a lot of problems—mainly around using Next.js and an API layer that seems to change with every new framework version 😛
In general, I see a lot of benefits in using SSG or ISR, but I don’t really see any for SSR where the page is rendered on every request.