What does Static Rendering and Dynamic Rendering terms mean?

[whole eagle]

I understand meaning of SSR, SSG and ISR
But While reading docs I come across Static Rendering and Dynamic Rendering terms, And I am confused.
Can anyone explain what does these terms mean?

[slender echo]

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)

[tawdry girder]

static = your path is statically = for/example/this/path/page.tsx
dynamic = your path has dynamic segements = for/example/[id]/path/page.tsx

It means, that dynamic stuff will be rendered on demand and static will be generated at build time and then just displayed.

You can see more about it here: https://nextjs.org/docs/app/building-your-application/rendering/server-components

[uncut hound]

static = your path is statically = for/example/this/path/page.tsx
dynamic = your path has dynamic segements = for/example/[id]/path/page.tsx
uhm no. static/dynamic rendering is purely whether a route is rendered in advance (e.g. during build time or ISR) or at request time. /this/path/page.tsx can be dynamically rendered and [id]/path/page.tsx can be statically rendered

[turbid flame]

i have a follow up question to this:

Advantage of statically rendered is that the (during build or revalidation time) generated page will be full-route cached by Nextjs and cached on the Vercel CDN in deployment?

While a dynamic rendered page will always skip full-route cache, however the data cache layer can still be implemented using something like fetch or unstable_cache?

I am 50:50 on the things i said so i'd appreciate your wisdom/clarification

[tawdry girder]

yes, of course it can, but I want to keep it simple and on the base of:

It means, that dynamic stuff will be rendered on demand and static will be generated at build time and then just displayed.

My on demand is your at request time
My generated at build time is your during build time

[uncut hound]

that's how i understand it but it's imo better to not understand it in terms of "full route cache" or similar terminologies. it will only make it more confusing.

cached on the Vercel CDN in deployment?
this part is dependent on the hosting platform and hosting methodology, and i don't research much into how vercel handles nextjs sites behind the scenes.

[uncut hound]

yes, but your example is extremely misleading. dynamic segment is completely different and separated from dynamic rendering and should not be implied to be similar.