What is Jamstack ?
Table of contents
No headings in the article.
JAMstack is software architecture and philosophy with an approach to fronted web development. It allows developers to quickly create and efficiently serve static website to users. JAMstack web application as much HTML as possible is pre built and stored in a content delivery network. Instead of running a monolithic backend application on the server side to generate dynamic content, dynamic components of the application are based on APIs that adheres to the following components :
:-What makes up the JAMstack?
Its history stems from growing the terms static site into something meaningful . So while a static site is the end result , its blown up to include first class tooling for every step of the way . There arn't specific tools that you need to use or any tools at all beyond simple HTML, there are great examples of what can make up each part of the stack.
What makes JAMstack so great?
JAMstack apps inherently satisfy most if not all of the 5 pillars of AWS Well Architected framework. These are core concept that AWS consider to deliver fast, secure, high performing, resilient and efficient infrastructure.
The fact thar you're serving JAMstack app as static files directly from CDN makes it likely your app is going to load superfast Gone are the days where the setver has to spend time building the page before responding now you serve the page as just plain HTML "as is" or with some type of client side hydration like you'd see with react.
More often that not, JAMstack site are going to run cheaper than their server side counterpart. Hosting static asset is cheap and now your page is being served at the same rate.
Since you're serving your files off static hosting likely a CDN that pretty much automatically gives you infinite scalability. Most providers will make this claim, meaning you'll have no trouble letting any influx of people hitting your site in through the front door.
The foundation of your static site isn't a server meaning you don't need to maintain it. Whether it's Netlify, S3 or any provider your static HTML , CSS and JS are maintained for your headache free.
Doubling down on the lack of server that you have to personally maintain you don't need to worry as much about looking down ways for the people to tribute. Instead, you'll need to focus mostly on permission to lock down private content and assure your users that their information isn't publically available.
Written by :Deepshikha Niyogi