This is my JAMstack

What is JAMstack?

Lets talk about an approach to building applications that may be more frontend developer-friendly. JAMstack is a concept or approach for building out applications if you want to create a website that does not require creating a server or database.

What is the JAMstack approach?

JAMstack stands for JavaScript, API, Markup. Typically when building out an application most developers are used to a Mololithinc structure. In a monolithic structure, the front end is tightly coupled with the backend. When the client makes a request, it hits a server, which pulls data from a database, that then produces HTML to render and then sends that back to the client. There is no need to build out the HTML page for every page request the client makes in the JAMstack structure.

The main concept behind JAMstack is to decouple the frontend from the backend and free the frontend from servers sp that it can be deployed directly to a CDN
With a JAMstack approach, the frontend pages are built before it is sent to the client through a build process before being deployed.
The JavaScript is the request/response cycle on the clients side.
The M in JAMstack stands for Markup. The markup are the static pages that are prebuilt and they are put in a CDN. So, if the client requests a page, there is no need to hit a server to build out the HTML, it instead will fetch the HTML from a CDN which has been pre-built.
The A in JAMstack is for the use of third party APIs which provide the dynamic content to the page. As well as querying requests to an API from the frontend before the pages are built to then deploy.

So, what are the benefits of using the JAMstack approach?

There are lots of benefits to this approach to building an application.
The first is that your website will be faster since it does not have to hit a server and the pages are prebuilt. Typically when you host your applications on servers with databases, users are making requests to the same servers in limited locations, which can cause traffic jams (pun intended). Instead, in JAMstack, you are deploying an application globally through the use of CDNs. A CDN (Content Delivery Network) distributes the static content, like the static content built in a JAMstack approach and then serves them to the users in a location closer to them. This also means higher security since there are no servers or databases in your application that are at risk. Because your pages are pre-built the performance of your application skyrockets as well.

Lastly, this makes the process of developing a site much easier, since there is no need to manage and build servers or databases. You can manage the content of your page through version control such as GIT. This approach to building an application makes sense if you have an application that does not require a full database and has content that can be built beforehand using markup.

Cover by Markus Spiske on Unsplash.