Nowadays, the static site generators are becoming very common because they are straightforward to use and they are based on the most modern technologies and JavaScript frameworks like Vue.js or React.

Thanks to static site generators, modern browsers, CDNs, and APIs, we’re now seeing web developers transition from server-side to client-side applications.

With all this, Netlify came out with a new term JAMstack.

So let’s see what the JAMstack is and why it is becoming so popular.

What is JAMstack?

JAMstack is not a technology. Instead, JAMstack is a new way of building websites and apps. It is a modern web development architecture based on client-side and it doesn’t depend on a web server.

A definition that I have read on a blog and I like a lot is

The JAMstack is a static HTML site, rebuilt automatically every time you update the content, and deployed directly to a CDN.

I think that this definition makes better the idea!

JAM stands for JavaScript, APIs, MArkup

JavaScript: any dynamic programming during the request/response cycle is handled by JS, running entirely on the client. This could be any frontend framework or library, or even vanilla JavaScript.

APIs: all server-side processes or database actions are abstracted into reusable APIs, accessed over HTTPS with JavaScript. These can be custom-built or leverage third-party services.

Markup: templated markup should be prebuilt at deploy time, usually using a site generator for content sites, or a build tool for web apps.

The Benefits provided by the JAMstack

Some of the main benefits of using it are the following

Faster and Better Performance

It can generate new pages at deploy time and serve pre-built markup and assets over a CDN.

Less expensive and easier to scale

The lesser complexity of development reduces costs and also hosting of static files is cheap or even free.

Higher Security

With the delegation of the server-side and database operations, we don’t need to worry about vulnerabilities anymore.

Better developer experience

Frontend developers can focus only on the frontend and debugging, the expanding selection of CMS options for site generators remove the need to maintain. This usually means quicker and more focused development.