Skip to content
dvnt.io

Resources · glossary

JAMstack

A way of building websites in which pages are generated in advance as ready files, and data comes from external services through APIs. The server does not assemble the page on every visit, so it is faster and cheaper.

Also called
  • JAMstack
  • Jamstack
  • static site generation
  • pre-rendered website
  1. 01

    Where the speed comes from

    From the fact that there is nothing to compute at the moment of the visit. The ready file sits closer to the user and only has to be sent — no database, no template assembly, no most common source of slow responses.

  2. 02

    What stops being a problem

    Traffic spikes and a large share of attacks. You cannot overload with queries a database that is not in the request path, or break in through a plugin that does not run on the server.

  3. 03

    Where it gets complicated

    With content that changes constantly and with very large sites — rebuilding thousands of pages takes time. There are ways around it (rebuilding only the changed pages), but they have to be planned rather than assuming the problem does not exist.

  4. 04

    Is it for you

    If your content changes a few times a day rather than a dozen times an hour — almost certainly yes. Our “WordPress or headless” quiz takes you through the same question from the editorial side rather than the technical one.

Related terms

  • Headless CMSA content management system that stores content and serves it through an API but does not dictate how the site looks. The presentation layer is built separately, usually in a modern framework.
  • SSR, SSG and CSR (rendering methods)Three answers to the question of where a page is built: on the server on every visit (SSR), in advance as a ready file (SSG), or in the user's browser (CSR). The choice shows in speed and in whether the search engine has anything to index.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.