简体中文
EnglishWhat is the Jamstack architecture approach?
Updated
Jamstack is an architectural approach that decouples the web experience layer from data and business logic. According to jamstack.org, this separation improves flexibility, scalability, performance, and maintainability. It removes the need for business logic to dictate the web experience, and it enables a composable architecture for the web where custom logic and third-party services are consumed through APIs.
The core idea: decoupling the experience layer
In a traditional setup, the thing that renders your pages is often tightly bound to the systems that store data and run business rules. Jamstack breaks that binding. The web experience layer — what users see and interact with — is separated from the data and logic behind it.
That means the front end does not have to be shaped by the constraints of the back end. You can change one without rebuilding the other.
How logic and services get consumed
Instead of embedding business logic directly into the experience layer, Jamstack relies on APIs. Custom logic and third-party services are consumed through those APIs. This is what jamstack.org describes as a composable architecture for the web: you assemble the capabilities you need from services rather than forcing everything through a single monolithic application.
What this approach is meant to improve
The source page lists four benefits that follow from this decoupling:
| Benefit | What it refers to |
|---|---|
| Flexibility | The experience layer and backend are independent, so each can evolve separately |
| Scalability | Decoupled architecture is easier to scale than a tightly coupled one |
| Performance | Separating the experience layer from business logic supports faster sites |
| Maintainability | Cleaner separation makes the system easier to maintain |
These are the stated goals of the approach, not guarantees for every implementation. How much you get from each depends on how you build.
Where the term comes from
Matt Biilmann took the concept of Jamstack mainstream with his presentation at Smashing Conf 2016. That talk is described by jamstack.org as the quintessential introduction to the Jamstack, and it remains the reference point for the original framing of the idea.
When this approach fits
Jamstack is worth considering when you want the web experience layer to be independent of the systems providing data and logic, and when you are comfortable consuming custom logic and third-party services through APIs. If your project depends on business logic directly dictating how pages are rendered, the decoupled model is a different trade-off and may not match that requirement.