JAMstack
Definition
A modern web architecture using JavaScript, APIs, and Markup to build fast, secure websites that are pre-built and served from a CDN.
Use Cases
- Smashing Magazine: High-traffic content site with fast global page loads and strong reliability requirements — Migrated parts of the site to a JAMstack-style approach using a static site generator to pre-render pages and deliver them via a CDN, while handling dynamic needs (such as search or interactive features) through APIs/services (Improved performance and resilience by serving pre-built pages from edge caches, reducing origin load and making pages feel faster for global readers)
- Nike: Marketing and campaign pages that must load quickly worldwide and scale during traffic spikes — Uses a decoupled front end delivered via CDN with dynamic commerce and personalization handled through APIs (a common JAMstack pattern for modern digital experiences) (Better scalability during peak demand and faster page delivery by caching and distributing pre-built assets globally)
Frequently Asked Questions
- What's the difference between JAMstack and a traditional server-rendered website (like WordPress or Rails)?
- In a traditional server-rendered site, each page request often triggers server-side work (rendering templates, querying a database) before the HTML is returned. In JAMstack, pages are usually generated ahead of time (at build time) and served as static files from a CDN, which is typically faster and reduces server attack surface. Dynamic features (comments, auth, search) are handled by calling APIs rather than rendering everything on the web server for every request.
- When should I use JAMstack?
- Use JAMstack when you want very fast load times, strong security, and easy scaling—especially for content sites, documentation, marketing pages, landing pages, and e-commerce front ends that can cache most pages. It’s a good fit when most content can be pre-rendered and dynamic features can be provided via APIs. Avoid or be cautious if your app requires highly personalized, per-request HTML for most pages or complex server-side workflows that are hard to express via APIs.
- How much does JAMstack cost?
- Costs usually come from (1) static hosting and CDN bandwidth/requests, (2) build minutes in CI/CD, and (3) API/back-end services used for dynamic features (serverless functions, databases, auth, search). Many JAMstack sites are inexpensive at low to moderate traffic because static files cache well, but costs can rise with high bandwidth usage, frequent rebuilds, or heavy API usage (for example, lots of authenticated requests or search queries).
Category: software
Difficulty: intermediate
Related Terms
See Also