JAM stack is defiantly going to shake the web industry over the next few years. Expect to hear the terms "Headless CMS", "Static site generator" and a-lot of fuss about page speed!
JAM Stack - I have never heard about it but looks very interesting.
I maybe wrong but isn't it similar to the existing JS based development ? Backend (NOde/Python/Java) provides APIs that can be used by the client -side frameworks like Vue, React. Seems to me that the only new thing is the pre-built markup which again sounds like cached version (in CDNs) of erstwhile server-side rendered templates.
Looked up few articles about it and seems like most of them talk about Re-usable APIs. And then give examples of Google API, TWILIO etc. So, do they mean APIs provided by external providers ? In that case how is it any reliable. We will be depending on those external providers for the complete maintenance of our backend logic
The big difference is the ideology. Instead of calling your APIs from the client we call them at build time then use a static site generator to generate the markup. This makes it super easy to host and makes your site super fast too.
JAM stack is defiantly going to shake the web industry over the next few years. Expect to hear the terms "Headless CMS", "Static site generator" and a-lot of fuss about page speed!
JAM Stack - I have never heard about it but looks very interesting.
I maybe wrong but isn't it similar to the existing JS based development ? Backend (NOde/Python/Java) provides APIs that can be used by the client -side frameworks like Vue, React. Seems to me that the only new thing is the pre-built markup which again sounds like cached version (in CDNs) of erstwhile server-side rendered templates.
Looked up few articles about it and seems like most of them talk about Re-usable APIs. And then give examples of Google API, TWILIO etc. So, do they mean APIs provided by external providers ? In that case how is it any reliable. We will be depending on those external providers for the complete maintenance of our backend logic
The big difference is the ideology. Instead of calling your APIs from the client we call them at build time then use a static site generator to generate the markup. This makes it super easy to host and makes your site super fast too.
So how do you accomodate changes required in the API ?
You don't have to, it's simply the client that's changing.