DEV Community

Divya
Divya

Posted on

Why choose the JAMstack?

There are many ways to build a website in 2020. From the more traditional approaches like LAMP and MEAN, to more modern ones like server side rendering (SSR) and the JAMstack, developers are spoilt for choice when it comes to picking a stack. While architectural choices vary based on use case, the JAMstack offers so much freedom of choice that it emerges as one of the most flexible stacks out there today. This flexibility is largely a result of the JAMstack’s focus on methodology over technology. Instead of prescribing what to use, the JAMstack converges on the why and how websites are built. With the JAMstack, developers are encouraged to build complexity consciously by choosing the various moving parts of their application and even outsourcing functionality to external APIs. Not only does this sort of decoupling reduce complexity and the cognitive load that follows it, it also makes JAMstack architectures more reusable. Other benefits of the JAMstack include significant performance boosts from serving static assets via a CDN, cost savings from not having to pre-scale servers, and greatly improved security from a reduced surface area for attack. The JAMstack offers all this and more in addition to a top notch developer experience. I'd say that's a pretty sweet deal.

If I’ve yet to convince you about the benefits of the JAMstack or if you'd like to dig in further, check out this fantastic book covering the wonders of the JAMstack over on the Netlify site.

Oldest comments (2)

Collapse
 
andevr profile image
drew

I'm going to go out on a limb and ask: What the hell is a JAMstack? :D

Collapse
 
tzmanics profile image
Tara Z. Manicsic

Well, how funny you should ask: dev.to/shortdiv/what-is-the-jamsta...