What is JAMStack?
Pre-rendering content during the build step, instead of relying on server-side rendering (SSR) simplifies deployment and allows websites to take advantage of long standing CDN technology. These CDNs allow for a global deployment which scales by design. The static nature of the files removes the need to server maintenance and adds additional security. Speed is everything in the world of commerce, especially during peak sales seasons. There is no faster option than static files served globally over a robust CDN.
The Building Blocks in a JAMStack Architecture:
APIs are also leveraged during both the build step and during website interactions. Since JAMStack is deployed to a static CDN, APIs must enable all server-side operations required. In a typical JAMStack ecommerce deployment, content and product data would be queries from the APIs during the build step and deployed as static assets. Dynamic actions including search, cart, and account data would involve API queries directly from the browser. For this reason, any API solutions adopted need to be extremely performance and able to handle both bursts of bulk API calls from a build server as well more sporadic API calls across the globe.
Markup can stand for multiple aspects of a JAMStack solution. It may represent markdown files leveraged for content and creation during the build step, JSON responses from the REST APIs, and perhaps most importantly the HTML (Hypertext Markup Language) that is compiled and served via content delivery network. This is the key benefit of JAMStack as having the core HTML rendered at build time, not runtime, ensures the best performance. This is especially true for JAMStack eCommerce websites who need consistent international performance which is built in to a CDN deployment as opposed to a single geographic server.