Server-Side Rendering (SSR)
In one sentence
Building complete HTML on the server so the browser can display it without executing application code first.
Analogy Mental model
The kitchen plates the dish and sends it out. The guest eats on arrival rather than cooking at the table.
In practice What you actually do
The default for frameworks that support it, and the simplest way to guarantee content is in the HTML. It costs server CPU per request, which is why caching in front of it is not optional at scale.
Where people get burned Pitfalls
Rendering on every request without a cache turns a traffic spike into an outage. The pattern that works is render once, cache at the edge, revalidate on publish.
This entry was written in English from the Chinese original, not machine-translated. Read the Chinese version →