{"id":16993,"date":"2019-09-09T08:03:32","date_gmt":"2019-09-09T06:03:32","guid":{"rendered":"https:\/\/www.inovex.de\/blog\/?p=16993"},"modified":"2026-02-19T07:31:36","modified_gmt":"2026-02-19T06:31:36","slug":"jamstack-apps-static-dynamic","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/jamstack-apps-static-dynamic\/","title":{"rendered":"JAMstack Apps: Static but Dynamic [State of the Web]"},"content":{"rendered":"

The JAMstack is not a new technology stack as the name might imply, but a new architecture for web applications. Instead of rendering a web site dynamically in the browser, this approach makes use of an old idea. It suggests to prerender HTML on deploy-time and to distribute the resulting static web app – but without the static experience. To achieve this the JAMstack makes use of J<\/strong>avaScript, A<\/strong>PIs, and M<\/strong>arkup.<\/p>\n

<\/p>\n

J<\/strong><\/span>avaScript handles everything that is happening between request-response-cycles and enables elements of a static site to become highly dynamic. Modern JavaScript frameworks such as ReactJS<\/a>, Angular<\/a> or VueJS<\/a> are well suited, for example.<\/p>\n

A<\/strong><\/span>PIs are required due to the fact that JAMstack apps are serverless. This means that there is no backend code required to be run on a server. Developers can solely focus on implementing their apps\u2019 frontend logic. Consequently common backend tasks such as saving user input, image processing, or authentication need to be handled by external services providing abstracted, public APIs.<\/p>\n

M<\/strong><\/span>arkup templates are prebuilt in the deployment process including the site\u2019s content. This can be accomplished with static site generators or other build tools for web applications. The content is stored in the shape of markdown files together with the project\u2019s source code on a version control platform such as GitLab or GitHub.<\/p>\n

\n

<\/p>\n<\/div>