March 08, 2019 | #code
High performance static websites for everyone.
I love fast, secure, light weight websites. Because JAMstack projects don’t rely on server-side code, they can be distributed instead of living on a single server. Serving directly from a CDN unlocks speeds and performance that can’t be beat. The more of your app you can push to the edge, the better the user experience.
Visit jamstack.org and you'll be greeted with the following:
JAMstack: noun \’jam-stak’\
Let’s dig into each of these items.
Templated markup should be prebuilt at deploy time, usually using a site generator for content sites, or a build tool for web apps.
When I first read this, I thought to myself “this seems like nothing new” and indeed, it really isn’t. What this stack represents is a set of rules which when complies yields a very secure, high performance site. So what problem does this approach try to solve? What are some possible use cases? Where does this stack fall apart?
The large majority of websites are simply serving up read-only content to users. What I mean by this is that most websites have upfront knowledge of the majority of content to be served (ex: a blog site). That said, the traditional client-server model starts to seem a bit inefficient.
Let’s think about that same blog example. If this site was built using WordPress there would be a lot of steps require to serve up this post.
This an extremely over simplified view of what actually happens however I hope you can see that this model has some flaws.
The traditional model of a client-server application is still extremely popular and widely used by many websites however it does have some downsides.