SSR

Question 1

Do Cliente Components run on the server during SSR?

Answer 1

Yes, Client Component renders on client and server, while Server Component just renders on server

Question 2

Is Window Object available on Server Side?

Answer 2

No

Question 3

What is the “golden rule” of hydration and SSR?

Answer 3

The very first render should produce the exact same markup on the server that it does on the client

Question 4

Two common footguns with SSR?

Answer 4

1, Trying to access “browser stuff” on the server
2, Hydration mismatches

Question 5

What is the “two-pass” strategy

Answer 5

First, we print the generic parts.
Second, when we have the specific information for each part, we do a second pass and fill those details

Question 6

SSR Flavor - “On-demand SSR”

Answer 6

The HTML is generated per-request

Question 7

SSR Flavor - “Static Site Generation”

Answer 7

The HMTL is generated for every route when the app is built

Question 8

SSR Flavor - “Incremental Static Regeneration”

Answer 8

Each route is rendered on-demand for the first request, but the HTML is saved for future requests

Question 9

What type of rendering strategy is used by Next.js in development mode?

Answer 9

dynamic on-demand SSR

Question 10

What type of rendering strategy is used by Next.js in production?

Answer 10

Next.js will try ti pick the optimal strategy on a route-by-route basis

Question 11

Server can stream the response?

Answer 11

Yes

Question 12

are allowed Server Components to be asynchronous?

Answer 12

Yes