5

So I've been reading a lot about this new front-end architecture called the JAMstack, which is basically the modern way of building static web applications. Any dynamic pages are pre-built at build time and served as static pages instead of being built on request at run time. This way, sites can be hosted on a CDN and any further dynamic behavior is handled on the client using JavaScript and APIs (serverless).

Now my question is, what is the difference between using a serverless architecture and the JAMstack? Is JAMstack just a fancy name for a purely serverless architecture? What would a serverless architecture look like that isn't considered JAMstack?

Any help clearing up the difference between these two terms would be greatly appreciated! I've tried finding an answer on Google, but couldn't find anything.

MikeRomero4
  • 69
  • 4

2 Answers2

4

I think you misunderstand the concept of 'Serverless' technology. IMO it's a very misleading and confusing name so you are not alone in this.

using JavaScript and APIs (serverless).

Using Javascript and APIs is not the definition of serverless. The client is not relevant at all to serverless technology. Here's a very in-depth article on serverless technology. It's quite long so here are my key takeaways:

  • The term really means two (related) things
    1. Vendor managed applications and services.
    2. Custom services that are deployed in a 'serverless' platform.
  • There are almost surely servers involved, you just don't deal with them
  • The main advantage is that you have essentially no cost when functions are not being used
  • The main disadvantage is that there is some latency when you need to "wake" up your function

It's possible that your APIs called by your web page are built on serverless technology but there's nothing about the scenario of 'a webpage using APIs' that implies this is the case.

JimmyJames supports Canada
  • 30,578
  • 3
  • 59
  • 108
-1

Jamstack and serverless have a lot of overlap. Jamstack’s goal is to serve your website or application from static storage. This static storage itself is serverless (you don’t manage it yourself), but that doesn’t mean that Jamstack is always serverless. For example, if you’re using Ruby for your backend, you’re not serverless.

Serverless, which is how you manage your backend, doesn’t mean that you’re developing with a Jamstack architecture but probably using some key components.

You can read more details here: https://snipcart.com/blog/jamstack-serverless-backend.

Ludovic
  • 1