The same happens here. Take an existing concept. Stick a new label-term on it. Market it like you're the inventor of this revolutionary concept to the unaware. Profit.
It makes tricks like React pages rendering without javascript possible, and works with pretty much any language that can manipulate strings (awk, sed & curl build process, why not).
If your api is only used during the build step, scaling is really easy like tfa mentions.
In pure JAMstack, APIs are used only at the build step, and you don't have to expose them. You get your content such as blog posts from the API, render them to html and store on CDN.
Monolithic architecture refers mostly to Wordpress. With JAMstack you separate your CMS from your frontend, and you can manage your content with a service like https://www.contentful.com/ that doesn't define how the content gets rendered.
The article is also loaded with BS:
> Faster performance. Serve pre-built markup and assets over a CDN
Just like every single-page app.
> More secure. No need to worry about server or database vulnerabilities
Total BS. A form post is an API call by another name. Your server and database are just as vulnerable via an API.
> Less expensive. Hosting of static files are cheap or even free
Just like every single-page app.
> Better developer experience. Front end developers can focus on the front end, without being tied to a monolithic architecture. This usually means quicker and more focused development
Really? And templating languages do not exist on the backend? The only difference is where the processing occurs, and a single-page app has just as much templating whether the template is rendered in-browser or on-server. Often it has a lot more.
> Scalability. If your product suddenly goes viral and has many active users, the CDN seamlessly compensates
Ahem! API?