Hello everyone, welcome to the last article of the JAMstack series, JAMstack for all. I am humbled and delighted with the likes, comments and feedback received on the previous articles so far.
If you are new to the series, here are the links to the previous articles. Hope you enjoy reading them.
Feel free to comment if you have questions or discussion points. You can follow me on twitter @tapasadhikary for any discussions and updates.
With all the background we have built so far, now is the time to see if JAMstack
is truly server less as it seemed. How are we going to make use of the JAMstack concept in enterprise applications which are complex and beyond a blogging kind of platform?
JAMstack
is a modern web development architecture based on client-side
JavaScript, reusable
APIs, and prebuilt
Markups. It is way different from any other technology stacks like LAMP
, MEAN
or MERN
where JAMstack
is more of a concept than, technology.
We have seen that, pre-building the markups give super power to make the applications or websites faster. Serving the prebuilt
markups from a CDN
infrastructure takes care of the blazing fast access, security and, cost.
I am sure, you remember this high level comparison between a monolithic application and JAMstacked application,
We have also made statements like,
_JAMstack_
_ is practically server less_
So far, our mode of understanding was about building something static using static site generators, host the files on CDN and serve to the end-users. This is fine for a portfolio site, a static web site, a blogging application, etc.
But what if, your app needs to,
What if your app needs the Dynamic Content
? Do you need server side programming to write, manage and maintain? It seems, you need to write custom back-ends. But, JAMstack
is server less, isn’t it?
#javascript #jamstack #aws #gcp #general programming