Discussion on "JAMstack vs traditional monolithic workflow"

Tapas Adhikary · 2020-08-23T09:44:00.574Z

Welcome to the second article of the series, JAMstack for All. Thank you for your likes, comments, and feedback on the JAMstack Introduction article. This article will be diving into the JAMstack workflow with a side-by-side comparison of the tradit...

@ doodle baseball, That is an abundance of excellent information. Regards, your contribution.

Amazing article but I am still confused between the traditional methods where we cache the webpages on CDN for better speed and using CDN for jamstack. How these two methods are different? I meant they both kinda doing the same.

Ashish maurya, The concept and usages are the same. The pages are pre-built(precompiled) and served from the nearest CDN of the requester is a key essential of Jamstack.

A traditional method that is doing the same is already in the bracket of Jamstack. It is entirely opposite of another traditional client-server approach where the server could be centralized, the pages are built and served on each request.

I hope, I was able to help in clarifying the doubt here?

Tapas Adhikary thanks for explaining. Its clear now.

This is a great series Tapas Adhikary, keep them coming 🥳

Thanks man Bolaji Ayodeji!

That's a lot of great info. Thanks for sharing.

Thanks Shad! Glad, that it was useful 😊

Discussion

JAMstack vs traditional monolithic workflow

Responses(3)

Recent in Forum

Search Hashnode

JAMstack vs traditional monolithic workflow

Responses(3)

Recent in Forum