What it is
Two ways of serving pages. SSR: the server builds the page on every request, handy for stores with live stock. Static: pages are built in advance and stored as files, the server has almost nothing to do and nothing to hack.
How we use it
The studio's Russian site runs as SSR in one container; the international one is built to static files on a server in Moldova. One project, two build modes.
Where it matters to a business
- A search robot must see products and texts immediately, not an empty page that JavaScript fills in later.
- Stock and prices change daily, and the page must show current ones.
- The site should open fast without needing a powerful server.
Types
- SSR: the server assembles the page on every request and delivers ready HTML. A store with stock and prices needs it.
- Static: pages are built in advance and stored as files. The server has almost nothing to do, and there is nothing to hack.
How we use it
- The online store runs as SSR: search engines see products at once, and the sitemap is built on the fly from visible products.
- The studio website: the Russian version is SSR in one container, while the international version of the same project is built as static files. One project, two build modes.
- The VPN guides are pure static pages on GitHub Pages, with no server at all.
Common problems
- SSR needs a server. The studio site's container needs 150 to 300 MB of memory, but the image has to be built on another machine.
- Static goes stale. Any edit requires a rebuild and a deploy, so it does not suit frequently changing prices.
When you do not need it
The owner does not have to choose: we decide by how often the data changes. Static for a business card, SSR for a store.