Websites are served as static HTML files. These can be generated from source files, such as Markdown, using a Static Site Generator.
Static site generators are not a new idea but most webhosting companies deploy new websites using WordPress, etc. where the content of pages/articles is stored on the server in a database. Static site generators on the other hand go in direction of static pages generated in advance and then serving them to the users directly via CDN.
On the other hand, Static Site Generators (SSG) work differently: if you request a page, the page in html format is already on the server side ready to be served nearly instantaneously, every piece of data on the page was prepared in advance and is served in the same manner to everyone who visits your page. Now let’s dive a little deeper.. All of your ‘content’ is written in .md files (Markdown) and this content is then injected within theme files (html templates) of your choice according to set of rules, it all depends on the chosen static site generator platform, where you start the build process that does this for you, this results in a static HTML page with content from the appropriate .md file and a look according to the chosen template. Development with the JAMstack architecture takes place mostly locally, but there are headless CMS systems out there that work with most of SSGs (more on that later). You can run the build process locally and just copy html files to your hosting or offload whole build process to your hosting provider end (if they support it) for finishing the deploy process, which places your html files on the CDN of your choice.
Well, since JAMstack content is generated during build and it is served using CDN, there is faster performance.
Considering you don’t need to worry about server/database vulnerabilities, it is also more secure.
Static files hosting is dirt cheap or even free..
From developers perspective, it is better experience, you can focus on front end without caring about architecture in the background. This also brings quicker development.
At last but not least it is scalable, CDN takes care of user-demand compensation :)
JAMstack workflow is quite simple, as an example we can take a look at this site and publishing of new blog post.
Once the content is ready, I simply commit my changes using git to my repository which is connected to Netlify for automated deployment. Netlify then starts build using Hugo static site generator, this build takes average of 30 seconds for my site since Hugo is extremely fast ;)
Once build is complete, Netlify publishes changes to its CDN and invalidates cache.
Changes are live from start to the end in up to one minute.. :)
As a footnote, there are services that combine all of the above mentioned features and advantages, one of those is stackbit, check it out !