Jamstack - A modern architecture
What is the JAMstack

You may have already seen or worked on a JAMstack site! They do not have to include all attributes of JavaScript, APIs, and Markup. They might be built using by hand, or with Jekyll, Hugo, Nuxt, Next, Gatsby, or another static site generator. The thing that they all have in common is that they don’t depend on a web server.

When is your site not built with the JAMstack

Any project that relies on a tight coupling between client and server is not built with the JAMstack. This would include:

1.A site built with a server-side CMS like WordPress, Drupal, Joomla, or Squarespace.

2. A monolithic server-run web app that relies on Ruby, Node, or another backend language.

3. A single page app that uses isomorphic rendering to build views on the server at runtime.

Why the JAMstack

1. Better Performance

Why wait for pages to build on the fly when you can generate them at deploy time? When it comes to minimizing the time to first byte, nothing beats pre-built files served over a CDN.

2. Higher Security

With server-side processes abstracted into microservice APIs, surface areas for attacks are reduced. You can also leverage the domain expertise of specialist third-party services.

3. Cheaper, Easier Scaling

When your deployment amounts to a stack of files that can be served anywhere, scaling is a matter of serving those files in more places. CDNs are perfect for this, and often include scaling in all of their plans.

4. Better Developer Experience

Loose coupling and separation of controls allow for more targeted development and debugging, and the expanding selection of CMS options for site generators remove the need to maintain a separate stack for content and marketing.