The Jamstack - what is it?
When I started to learn web developing I looked into hundreds of different platforms and languages to try and find what I thought was the best use case scenario for the majority of my clients.
This is where the Jamstack stepped in.
What is the Jamstack?
As described by the “Jamstack is an architecture designed to make the web faster, more secure, and easier to scale”. What does this mean in reality?
- Faster Websites - Pages can be rendered on build time saving a lot of time on delivery to the visitor and also providing a search engine friendly static generated version that it can crawl.
- More Secure - by nature the Jamstack has less moving parts and is also less complex, only loading needed code.
- Pre-Rendered sites - this means it is easier to scale and less computing power is needed to do so. WordPress sites are essentially an application running on a server, building pages on request constantly needing to contact a database for information in this case MySQL.
- Hosting - The majority of Jamstack specific hosts offer incredibly fast global CDNs out of the box.
There are a whole host of different Jamstack platforms for us to use with some of the most popular being Next.JS, Gatsby.JS, Vue.JS, 11ty, Hugo and the list goes on.
Out of all the options above I settled on , which really stood out to me for many reasons:
- Vercel - The creators of Next is a company called vercel and they have released incredibly detailed documentation and even some of the developers have videos on how to solve some complex problems
- Community - Next was launched in 2016 and the community has grown and is incredibly helpful with many public repos to explore
As you can see for me Next.js was best fit and it just works how you expect it to work, experiencing almost no bugs and on the occasion you do find one, the community always seems to already have a work around. Next has allowed me to produce websites of speeds I didn't think was possible.
Jamstack works by decoupling the backend from the frontend which could mean we lose our CMS. WordPress for example comes with a CMS out the box allowing clients to make changes to web pages. But what if we could use a CMS which instead of using a database and dynamically creating web pages, we could use a Git workflow.
has made this possible, we simply edit specific files changing the text or data needed then rebuild the webpage, once again statically generating the page for fast load speed. What’s more the CMS is created using React so we know it's going to be fast and secure. The Netlify CMS means we don't need an over-complicated backend to run the CMS, this means most websites won’t even need a database and just to make it even sweeter the files are backed up to your chosen git provider such as GitHub or GitLab.
How much would a Jamstack website cost? This is something that really depends on your use case and the size of the website however, seeing some of the huge figures that people charge for WordPress sites, I strongly believe by finding the right developer, someone with a passion for the industry and the technical know how like myself, you could still pick up a hand coded Jamstack website for much cheaper than someone offering a WordPress site.
I spoke previously about how website speed is a major factor to user experience and again I am left asking myself why I would use anything else? Why wouldn't we want to take advantage of everything the Jamstack offers?
- Fast websites
- Built in security
- Smaller load sizes
- Less need to update systems
- Less bugs
If you have any questions about my experiences or want advice on how to switch to Jamstack let me know.
3rd September 2021